Systems and methods for deriving a motion vector difference in video coding

ABSTRACT

A method of deriving a motion vector difference for coding video data, the method comprises determining whether inter-layer prediction is utilized by determining whether both a reference picture in a first reference picture list is not marked as used for long-term reference and a reference picture in a second reference picture list is not marked as used for long-term reference; based on whether the inter-layer prediction is utilized, setting a scaling factor to one of: a value of 1 in a case where the inter-layer prediction is utilized; or a value in the range of −4096 to 4095 in a case where the inter-layer prediction is not utilized; and deriving the motion vector difference based on the scaling factor.

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims priority from Provisional Application Nos. 63/050,462 and 63/056,994, the contents of which are hereby incorporated by reference into this application.

TECHNICAL FIELD

This disclosure relates to video coding and more particularly to techniques for deriving a motion vector difference for coded video.

BACKGROUND

Digital video capabilities can be incorporated into a wide range of devices, including digital televisions, laptop or desktop computers, tablet computers, digital recording devices, digital media players, video gaming devices, cellular telephones, including so-called smartphones, medical imaging devices, and the like. Digital video may be coded according to a video coding standard. Video coding standards define the format of a compliant bitstream encapsulating coded video data. A compliant bitstream is a data structure that may be received and decoded by a video decoding device to generate reconstructed video data. Video coding standards may utilize video compression techniques. Examples of video coding standards include ISO/IEC MPEG-4 Visual and ITU-T H.264 (also known as ISO/IEC MPEG-4 AVC) and High-Efficiency Video Coding (HEVC). HEVC is described in High Efficiency Video Coding (HEVC), Rec. ITU-T H.265, December 2016, which is incorporated by reference, and referred to herein as ITU-T H.265. Extensions and improvements for ITU-T H.265 are currently being considered for the development of next generation video coding standards. For example, the ITU-T Video Coding Experts Group (VCEG) and ISO/IEC (Moving Picture Experts Group (MPEG) (collectively referred to as the Joint Video Exploration Team (JVET)) are working to standardized video coding technology with a compression capability that significantly exceeds that of the current HEVC standard. The Joint Exploration Model 7 (JEM 7), Algorithm Description of Joint Exploration Test Model 7 (JEM 7), ISO/IEC JTC1/SC29/WG11 Document: JVET-G1001, July 2017, Torino, IT, which is incorporated by reference herein, describes the coding features that were under coordinated test model study by the JVET as potentially enhancing video coding technology beyond the capabilities of ITU-T H.265. It should be noted that the coding features of JEM 7 are implemented in JEM reference software. As used herein, the term JEM may collectively refer to algorithms included in JEM 7 and implementations of JEM reference software. Further, in response to a “Joint Call for Proposals on Video Compression with Capabilities beyond HEVC,” jointly issued by VCEG and MPEG, multiple descriptions of video coding tools were proposed by various groups at the 10^(th) Meeting of ISO/IEC JTC1/SC29/WG11 16-20 Apr. 2018, San Diego, Calif. From the multiple descriptions of video coding tools, a resulting initial draft text of a video coding specification is described in “Versatile Video Coding (Draft 1),” 10^(th) Meeting of ISO/IEC JTC1/SC29/WG11 16-20 Apr. 2018, San Diego, Calif., document JVET-J1001-v2, which is incorporated by reference herein, and referred to as JVET-J1001. The current development of a next generation video coding standard by the VCEG and MPEG is referred to as the Versatile Video Coding (VVC) project. “Versatile Video Coding (Draft 10),” 19th Meeting of ISO/IEC JTC1/SC29/WG11 22 Jun. 2020-1 Jul. 2020, Teleconference, document JVET-S2001-vA, which is incorporated by reference herein, and referred to as JVET-S2001, represents the current iteration of the draft text of a video coding specification corresponding to the VVC project.

Video compression techniques enable data requirements for storing and transmitting video data to be reduced. Video compression techniques may reduce data requirements by exploiting the inherent redundancies in a video sequence. Video compression techniques may sub-divide a video sequence into successively smaller portions (i.e., groups of pictures within a video sequence, a picture within a group of pictures, regions within a picture, sub-regions within regions, etc.). Intra prediction coding techniques (e.g., spatial prediction techniques within a picture) and inter prediction techniques (i.e., inter-picture techniques (temporal)) may be used to generate difference values between a unit of video data to be coded and a reference unit of video data. The difference values may be referred to as residual data. Residual data may be coded as quantized transform coefficients. Syntax elements may relate residual data and a reference coding unit (e.g., intra-prediction mode indices, and motion information). Residual data and syntax elements may be entropy coded. Entropy encoded residual data and syntax elements may be included in data structures forming a compliant bitstream.

SUMMARY

In general, this disclosure describes various techniques for coding video data. In particular, this disclosure describes techniques for deriving motion vector differences. It should be noted that although techniques of this disclosure are described with respect to ITU-T H.264, ITU-T H.265, JEM, and JVET-52001, the techniques of this disclosure are generally applicable to video coding. For example, the coding techniques described herein may be incorporated into video coding systems, (including video coding systems based on future video coding standards) including video block structures, intra prediction techniques, inter prediction techniques, transform techniques, filtering techniques, and/or entropy coding techniques other than those included in ITU-T H.265, JEM, and JVET-S2001. Thus, reference to ITU-T H.264, ITU-T H.265, JEM, and/or JVET-52001 is for descriptive purposes and should not be construed to limit the scope of the techniques described herein. Further, it should be noted that incorporation by reference of documents herein is for descriptive purposes and should not be construed to limit or create ambiguity with respect to terms used herein. For example, in the case where an incorporated reference provides a different definition of a term than another incorporated reference and/or as the term is used herein, the term should be interpreted in a manner that broadly includes each respective definition and/or in a manner that includes each of the particular definitions in the alternative.

In one example, a method of deriving a motion vector difference for coding video data, the method comprises: determining whether inter-layer prediction is utilized by determining whether both a reference picture in a first reference picture list is not marked as used for long-term reference and a reference picture in a second reference picture list is not marked as used for long-term reference; based on whether the inter-layer prediction is utilized, setting a scaling factor to one of: a value of 1 in a case where the inter-layer prediction is utilized; or a value in the range of −4096 to 4095 in a case where the inter-layer prediction is not utilized; and deriving the motion vector difference based on the scaling factor.

In one example, a device of deriving a motion vector difference for coding video data, the device comprises one or more processors configured to: determine whether inter-layer prediction is utilized by determining whether both a reference picture in a first reference picture list is not marked as used for long-term reference and a reference picture in a second reference picture list is not marked as used for long-term reference; based on whether the inter-layer prediction is utilized, set a scaling factor to one of: a value of 1 in a case where the inter-layer prediction is utilized; or a value in the range of −4096 to 4095 in a case where the inter-layer prediction is not utilized; and derive the motion vector difference based on the scaling factor.

In one example, a non-transitory computer-readable storage medium comprises instructions stored thereon that, when executed, cause one or more processors of a device to: determine whether inter-layer prediction is utilized by determining whether both a reference picture in a first reference picture list is not marked as used for long-term reference and a reference picture in a second reference picture list is not marked as used for long-term reference; based on whether the inter-layer prediction is utilized, set a scaling factor to one of: a value of 1 in a case where the inter-layer prediction is utilized; or a value in the range of −4096 to 4095 in a case where the inter-layer prediction is not utilized; and derive the motion vector difference based on the scaling factor.

The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating an example of a system that may be configured to encode and decode video data according to one or more techniques of this disclosure.

FIG. 2 is a conceptual diagram illustrating coded video data and corresponding data structures according to one or more techniques of this disclosure.

FIG. 3 is a conceptual diagram illustrating a data structure encapsulating coded video data and corresponding metadata according to one or more techniques of this disclosure.

FIG. 4 is a conceptual drawing illustrating an example of components that may be included in an implementation of a system that may be configured to encode and decode video data according to one or more techniques of this disclosure.

FIG. 5 is a block diagram illustrating an example of a video encoder that may be configured to encode video data according to one or more techniques of this disclosure.

FIG. 6 is a block diagram illustrating an example of a video decoder that may be configured to decode video data according to one or more techniques of this disclosure.

DETAILED DESCRIPTION

Video content includes video sequences comprised of a series of frames (or pictures). A series of frames may also be referred to as a group of pictures (GOP). Each video frame or picture may divided into one or more regions. Regions may be defined according to a base unit (e.g., a video block) and sets of rules defining a region. For example, a rule defining a region may be that a region must be an integer number of video blocks arranged in a rectangle. Further, video blocks in a region may be ordered according to a scan pattern (e.g., a raster scan). As used herein, the term video block may generally refer to an area of a picture or may more specifically refer to the largest array of sample values that may be predictively coded, sub-divisions thereof, and/or corresponding structures. Further, the term current video block may refer to an area of a picture being encoded or decoded. A video block may be defined as an array of sample values. It should be noted that in some cases pixel values may be described as including sample values for respective components of video data, which may also be referred to as color components, (e.g., luma (Y) and chroma (Cb and Cr) components or red, green, and blue components). It should be noted that in some cases, the terms pixel value and sample value are used interchangeably. Further, in some cases, a pixel or sample may be referred to as a pel. A video sampling format, which may also be referred to as a chroma format, may define the number of chroma samples included in a video block with respect to the number of luma samples included in a video block. For example, for the 4:2:0 sampling format, the sampling rate for the luma component is twice that of the chroma components for both the horizontal and vertical directions.

A video encoder may perform predictive encoding on video blocks and sub-divisions thereof. Video blocks and sub-divisions thereof may be referred to as nodes. ITU-T H.264 specifies a macroblock including 16×16 luma samples. That is, in ITU-T H.264, a picture is segmented into macroblocks. ITU-T H.265 specifies an analogous Coding Tree Unit (CTU) structure (which may be referred to as a largest coding unit (LCU)). In ITU-T H.265, pictures are segmented into CTUs. In ITU-T H.265, for a picture, a CTU size may be set as including 16×16, 32×32, or 64×64 luma samples. In ITU-T H.265, a CTU is composed of respective Coding Tree Blocks (CTB) for each component of video data (e.g., luma (Y) and chroma (Cb and Cr). It should be noted that video having one luma component and the two corresponding chroma components may be described as having two channels, i.e., a luma channel and a chroma channel. Further, in ITU-T H.265, a CTU may be partitioned according to a quadtree (QT) partitioning structure, which results in the CTBs of the CTU being partitioned into Coding Blocks (CB). That is, in ITU-T H.265, a CTU may be partitioned into quadtree leaf nodes. According to ITU-T H.265, one luma CB together with two corresponding chroma CBs and associated syntax elements are referred to as a coding unit (CU). In ITU-T H.265, a minimum allowed size of a CB may be signaled. In ITU-T H.265, the smallest minimum allowed size of a luma CB is 8×8 luma samples. In ITU-T H.265, the decision to code a picture area using intra prediction or inter prediction is made at the CU level.

In ITU-T H.265, a CU is associated with a prediction unit structure having its root at the CU. In ITU-T H.265, prediction unit structures allow luma and chroma CBs to be split for purposes of generating corresponding reference samples. That is, in ITU-T H.265, luma and chroma CBs may be split into respective luma and chroma prediction blocks (PBs), where a PB includes a block of sample values for which the same prediction is applied. In ITU-T H.265, a CB may be partitioned into 1, 2, or 4 PBs. ITU-T H.265 supports PB sizes from 64×64 samples down to 4×4 samples. In ITU-T H.265, square PBs are supported for intra prediction, where a CB may form the PB or the CB may be split into four square PBs. In ITU-T H.265, in addition to the square PBs, rectangular PBs are supported for inter prediction, where a CB may be halved vertically or horizontally to form PBs. Further, it should be noted that in ITU-T H.265, for inter prediction, four asymmetric PB partitions are supported, where the CB is partitioned into two PBs at one quarter of the height (at the top or the bottom) or width (at the left or the right) of the CB. Intra prediction data (e.g., intra prediction mode syntax elements) or inter prediction data (e.g., motion data syntax elements) corresponding to a PB is used to produce reference and/or predicted sample values for the PB.

JEM specifies a CTU having a maximum size of 256×256 luma samples. JEM specifies a quadtree plus binary tree (QTBT) block structure. In JEM, the QTBT structure enables quadtree leaf nodes to be further partitioned by a binary tree (BT) structure. That is, in JEM, the binary tree structure enables quadtree leaf nodes to be recursively divided vertically or horizontally. In JVET-S2001, CTUs are partitioned according a quadtree plus multi-type tree (QTMT or QT+MTT) structure. The QTMT in JVET-S2001 is similar to the QTBT in JEM. However, in JVET-S2001, in addition to indicating binary splits, the multi-type tree may indicate so-called ternary (or triple tree (TT)) splits. A ternary split divides a block vertically or horizontally into three blocks. In the case of a vertical TT split, a block is divided at one quarter of its width from the left edge and at one quarter its width from the right edge and in the case of a horizontal TT split a block is at one quarter of its height from the top edge and at one quarter of its height from the bottom edge.

As described above, each video frame or picture may be divided into one or more regions. For example, according to ITU-T H.265, each video frame or picture may be partitioned to include one or more slices and further partitioned to include one or more tiles, where each slice includes a sequence of CTUs (e.g., in raster scan order) and where a tile is a sequence of CTUs corresponding to a rectangular area of a picture. It should be noted that a slice, in ITU-T H.265, is a sequence of one or more slice segments starting with an independent slice segment and containing all subsequent dependent slice segments (if any) that precede the next independent slice segment (if any). A slice segment, like a slice, is a sequence of CTUs. Thus, in some cases, the terms slice and slice segment may be used interchangeably to indicate a sequence of CTUs arranged in a raster scan order. Further, it should be noted that in ITU-T H.265, a tile may consist of CTUs contained in more than one slice and a slice may consist of CTUs contained in more than one tile. However, ITU-T H.265 provides that one or both of the following conditions shall be fulfilled:(1) All CTUs in a slice belong to the same tile; and (2) All CTUs in a tile belong to the same slice.

With respect to JVET-S2001, slices are required to consist of an integer number of complete tiles or an integer number of consecutive complete CTU rows within a tile, instead of only being required to consist of an integer number of CTUs. It should be noted that in JVET-S2001, the slice design does not include slice segments (i.e., no independent/dependent slice segments). Thus, in JVET-S2001, a picture may include a single tile, where the single tile is contained within a single slice or a picture may include multiple tiles where the multiple tiles (or CTU rows thereof) may be contained within one or more slices. In JVET-S2001, the partitioning of a picture into tiles is specified by specifying respective heights for tile rows and respective widths for tile columns. Thus, in JVET-S2001 a tile is a rectangular region of CTUs within a particular tile row and a particular tile column position. Further, it should be noted that JVET-S2001 provides where a picture may be partitioned into subpictures, where a subpicture is a rectangular region of a CTUs within a picture. The top-left CTU of a subpicture may be located at any CTU position within a picture with subpictures being constrained to include one or more slices Thus, unlike a tile, a subpicture is not necessarily limited to a particular row and column position. It should be noted that subpictures may be useful for encapsulating regions of interest within a picture and a sub-bitstream extraction process may be used to only decode and display a particular region of interest. That is, as described in further detail below, a bitstream of coded video data includes a sequence of network abstraction layer (NAL) units, where a NAL unit encapsulates coded video data, (i.e., video data corresponding to a slice of picture) or a NAL unit encapsulates metadata used for decoding video data (e.g., a parameter set) and a sub-bitstream extraction process forms a new bitstream by removing one or more NAL units from a bitstream.

FIG. 2 is a conceptual diagram illustrating an example of a picture within a group of pictures partitioned according to tiles, slices, and subpictures. It should be noted that the techniques described herein may be applicable to tiles, slices, subpictures, sub-divisions thereof and/or equivalent structures thereto. That is, the techniques described herein may be generally applicable regardless of how a picture is partitioned into regions. For example, in some cases, the techniques described herein may be applicable in cases where a tile may be partitioned into so-called bricks, where a brick is a rectangular region of CTU rows within a particular tile. Further, for example, in some cases, the techniques described herein may be applicable in cases where one or more tiles may be included in so-called tile groups, where a tile group includes an integer number of adjacent tiles. In the example illustrated in FIG. 2 , Pic₃ is illustrated as including 16 tiles (i.e., Tile₀ to Tile₁₅) and three slices (i.e., Slice₀ to Slice₂). In the example illustrated in FIG. 2 , Slice₀ includes four tiles (i.e., Tile₀ to Tile₃), Slices includes eight tiles (i.e., Tile₄ to Tilers), and Slice₂ includes four tiles (i.e., Tile₁₂ to Tile₁₅). Further, as illustrated in the example of FIG. 2 , Pic₃ is illustrated as including two subpictures (i.e., Subpicture₀ and Subpicture₁), where Subpicture₀ includes Slice₀ and Slices and where Subpictures includes Slice₂. As described above, subpictures may be useful for encapsulating regions of interest within a picture and a sub-bitstream extraction process may be used in order to selectively decode (and display) a region interest. For example, referring to FIG. 2 , Subpicture₀ may corresponding to an action portion of a sporting event presentation (e.g., a view of the field) and Subpicture₁ may corresponding to a scrolling banner displayed during the sporting event presentation. By using organizing a picture into subpictures in this manner, a viewer may be able to disable the display of the scrolling banner. That is, through a sub-bitstream extraction process Slice₂ NAL unit may be removed from a bitstream (and thus not decoded and/or displayed) and Slice₀ NAL unit and Slices NAL unit may be decoded and displayed. The encapsulation of slices of a picture into respective NAL unit data structures and sub-bitstream extraction are described in further detail below.

For intra prediction coding, an intra prediction mode may specify the location of reference samples within a picture. In ITU-T H.265, defined possible intra prediction modes include a planar (i.e., surface fitting) prediction mode, a DC (i.e., flat overall averaging) prediction mode, and 33 angular prediction modes (predMode:2-34). In JEM, defined possible intra-prediction modes include a planar prediction mode, a DC prediction mode, and 65 angular prediction modes. It should be noted that planar and DC prediction modes may be referred to as non-directional prediction modes and that angular prediction modes may be referred to as directional prediction modes. It should be noted that the techniques described herein may be generally applicable regardless of the number of defined possible prediction modes.

For inter prediction coding, a reference picture is determined and a motion vector (MV) identifies samples in the reference picture that are used to generate a prediction for a current video block. For example, a current video block may be predicted using reference sample values located in one or more previously coded picture(s) and a motion vector is used to indicate the location of the reference block relative to the current video block. A motion vector may describe, for example, a horizontal displacement component of the motion vector (i.e., MV_(x)), a vertical displacement component of the motion vector (i.e., MV_(y)), and a resolution for the motion vector (e.g., one-quarter pixel precision, one-half pixel precision, one-pixel precision, two-pixel precision, four-pixel precision). Previously decoded pictures, which may include pictures output before or after a current picture, may be organized into one or more to reference pictures lists and identified using a reference picture index value. Further, in inter prediction coding, uni-prediction refers to generating a prediction using sample values from a single reference picture and bi-prediction refers to generating a prediction using respective sample values from two reference pictures. That is, in uni-prediction, a single reference picture and corresponding motion vector are used to generate a prediction for a current video block and in bi-prediction, a first reference picture and corresponding first motion vector and a second reference picture and corresponding second motion vector are used to generate a prediction for a current video block. In bi-prediction, respective sample values are combined (e.g., added, rounded, and clipped, or averaged according to weights) to generate a prediction. Pictures and regions thereof may be classified based on which types of prediction modes may be utilized for encoding video blocks thereof. That is, for regions having a B type (e.g., a B slice), bi-prediction, uni-prediction, and intra prediction modes may be utilized, for regions having a P type (e.g., a P slice), uni-prediction, and intra prediction modes may be utilized, and for regions having an I type (e.g., an I slice), only intra prediction modes may be utilized. As described above, reference pictures are identified through reference indices. For example, for a P slice, there may be a single reference picture list, RefPicList0 and for a B slice, there may be a second independent reference picture list, RefPicList1, in addition to RefPicList0. It should be noted that for uni-prediction in a B slice, one of RefPicList0 or RefPicList1 may be used to generate a prediction. Further, it should be noted that during the decoding process, at the onset of decoding a picture, reference picture list(s) are generated from previously decoded pictures stored in a decoded picture buffer (DPB).

Further, a coding standard may support various modes of motion vector prediction. Motion vector prediction enables the value of a motion vector for a current video block to be derived based on another motion vector. For example, a set of candidate blocks having associated motion information may be derived from spatial neighboring blocks and temporal neighboring blocks to the current video block. Further, generated (or default) motion information may be used for motion vector prediction. Examples of motion vector prediction include advanced motion vector prediction (AMVP), temporal motion vector prediction (TMVP), so-called “merge” mode, and “skip” and “direct” motion inference. Further, other examples of motion vector prediction include advanced temporal motion vector prediction (ATMVP) and Spatial-temporal motion vector prediction (STMVP). For motion vector prediction, both a video encoder and video decoder perform the same process to derive a set of candidates. Thus, for a current video block, the same set of candidates is generated during encoding and decoding.

As described above, for inter prediction coding, reference samples in a previously coded picture are used for coding video blocks in a current picture. Previously coded pictures which are available for use as reference when coding a current picture are referred as reference pictures. It should be noted that the decoding order does not necessary correspond with the picture output order, i.e., the temporal order of pictures in a video sequence. In ITU-T H.265, when a picture is decoded it is stored to a decoded picture buffer (DPB) (which may be referred to as frame buffer, a reference buffer, a reference picture buffer, or the like). In ITU-T H.265, pictures stored to the DPB are removed from the DPB when they been output and are no longer needed for coding subsequent pictures. In ITU-T H.265, a determination of whether pictures should be removed from the DPB is invoked once per picture, after decoding a slice header, i.e., at the onset of decoding a picture. For example, referring to FIG. 2 , Pic₂ is illustrated as referencing Pic₁. Similarly, Pic₃ is illustrated as referencing Pic₀. With respect to FIG. 2 , assuming the picture number corresponds to the decoding order, the DPB would be populated as follows: after decoding Pic₀, the DPB would include {Pic₀}; at the onset of decoding Pic_(k) the DPB would include {Pic₀}; after decoding Pic_(k) the DPB would include {Pic₀, Pic₁}; at the onset of decoding Pic₂, the DPB would include {Pic₀, Pic₁}. Pic₂ would then be decoded with reference to Pic₁ and after decoding Pic₂, the DPB would include {Pic₀, Pic₁ Pic₂}. At the onset of decoding Pic₃, pictures Pic₀ and Pic₁ would be marked for removal from the DPB, as they are not needed for decoding Pic₃ (or any subsequent pictures, not shown) and assuming Pic₁ and Pic₂ have been output, the DPB would be updated to include {Pic₀}. Pic₃ would then be decoded by referencing Pic₀. The process of marking pictures for removal from a DPB may be referred to as reference picture set (RPS) management.

With respect to the equations used herein, the following arithmetic operators may be used:

-   -   + Addition     -   − Subtraction     -   * Multiplication, including matrix multiplication     -   x^(Y) Exponentiation. Specifies x to the power of y. In other         contexts, such notation is used for superscripting not intended         for interpretation as exponentiation.     -   / Integer division with truncation of the result toward zero.         For example, 7/4 and −7/−4 are truncated to 1 and − 7/4 and 7/−4         are truncated to −1.     -   ÷ Used to denote division in mathematical equations where no         truncation or rounding is intended.

$\frac{x}{y}$

Used to denote division in mathematical equations where no truncation or rounding is intended.

Further, the following mathematical functions may be used:

Log2(x) the base-2 logarithm of x;

${{{Min}\left( {x,y} \right)} =^{\{\begin{matrix} {x\ ;} & {x<=y} \\ {y\ ;} & {x > y} \end{matrix}}};$ ${{Max}\left( {x,y} \right)} =^{\{\begin{matrix} {x;} & {x>=y} \\ {y\ ;} & {x < y} \end{matrix}}$

Ceil(x) the smallest integer greater than or equal to x.

${{Clip}3\left( {x,y,\ z} \right)} = \left\{ \begin{matrix} {x;} & {z < x} \\ {y;} & {z > y} \\ {z;} & {otherwise} \end{matrix} \right.$

With respect to the example syntax used herein, the following definitions of logical operators may be applied:

x && y Boolean logical “and” of x and y x∥y Boolean logical “or” of x and y ! Boolean logical “not” x?y: z If x is TRUE or not equal to 0, evaluates to the value of y; otherwise, evaluates to the value of z.

Further, the following relational operators may be applied:

-   -   > Greater than     -   >=Greater than or equal to     -   < Less than     -   <=Less than or equal to     -   =Equal to     -   !=Not equal to

Further, it should be noted that in the syntax descriptors used herein, the following descriptors may be applied:

-   -   b(8): byte having any pattern of bit string (8 bits). The         parsing process for this descriptor is specified by the return         value of the function read_bits(8).     -   f(n): fixed-pattern bit string using n bits written (from left         to right) with the left bit first. The parsing process for this         descriptor is specified by the return value of the function         read_bits(n).     -   se(v): signed integer 0-th order Exp-Golomb-coded syntax element         with the left bit first.     -   tb(v): truncated binary using up to maxVal bits with maxVal         defined in the semantics of the symtax element.     -   tu(v): truncated unary using up to maxVal bits with maxVal         defined in the semantics of the symtax element.     -   u(n): unsigned integer using n bits. When n is “v” in the syntax         table, the number of bits varies in a manner dependent on the         value of other syntax elements. The parsing process for this         descriptor is specified by the return value of the function         read_bits(n) interpreted as a binary representation of an         unsigned integer with most significant bit written first.     -   ue(v): unsigned integer 0-th order Exp-Golomb-coded syntax         element with the left bit first.

It should be noted that JVET-S2001 provides the following functions:

The function PicOrderCnt(picX) is specified as follows:

PicOrderCnt(picX)=PicOrderCntVal of the picture picX

The function DiffPicOrderCnt(picA, picB) is specified as follows:

DiffPicOrderCnt(picA, picB)=PicOrderCnt(picA)−PicOrderCnt(picB)

The bitstream shall not contain data that result in values of DiffPicOrderCnt(picA, picB) used in the decoding process that are not in the range of −2¹⁵ to 2¹⁵ — 1, inclusive.

-   -   NOTE— Let X be the current picture and Y and Z be two other         pictures in the same CVS, Y and Z are considered to be in the         same output order direction from X when both         DiffPicOrderCnt(X, Y) and DiffPicOrderCnt(X, Z) are positive or         both are negative.

As described above, motion vector prediction enables the value of a motion vector for a current video block to be derived based on another motion vector. JVET-S2001 includes a so-called merge mode with motion vector difference. That is, JVET-S2001 provides the following merge data syntax:

TABLE 1 merge_data( x0, y0, cbWidth, cbHeight, chType ) { Descriptor  if( CuPredMode[ chType ][ x0 ][ y0 ] = = MODE_IBC ) {   if( MaxNumIbcMergeCand > 1 )    merge_idx[ x0 ][ y0 ] ae(v)  } else {   if( MaxNumSubblockMergeCand > 0 && cbWidth >= 8 && cbHeight >= 8 )    merge_subblock_flag[ x0 ][ y0 ] ae(v)   if( merge_subblock_flag[ x0 ][ y0 ] = = 1 ) {    if( MaxNumSubblockMergeCand > 1 )     merge_subblock_idx[ x0 ][ y0 ] ae(v)   } else {    if( cbWidth < 128 && cbHeight < 128 &&      ( ( sps_ciip_enabled_flag && cu_skip_flag[ x0 ][ y0 ] = = 0 &&       ( cbWidth * cbHeight) >= 64 ) | |      ( sps_gpm_enabled_flag &&      sh_slice_type = = B && cbWidth >= 8 && cbHeight >= 8 &&      cbWidth < ( 8 * cbHeight ) && cbHeight < ( 8 * cbWidth ) ) ) )     regular_merge_flag[ x0 ][ y0 ] ae(v)    if( regular_merge_flag[ x0 ][ y0 ] = = 1 ) {     if( sps_mmvd_enabled_flag )      mmvd_merge_flag[ x0 ][ y0 ] ae(v)     if( mmvd_merge_flag[ x0 ][ y0 ] = = 1 ) {      if( MaxNumMergeCand > 1 )       mmvd_cand_flag[ x0 ][ y0 ] ae(v)      mmvd_distance_idx[ x0 ][ y0 ] ae(v)      mmvd_direction_idx[ x0 ][ y0 ] ae(v)     } else if( MaxNumMergeCand > 1 )      merge_idx[ x0 ][ y0 ] ae(v)    } else {     if( sps_ciip_enabled_flag && sps_gpm_enabled_flag &&      sh_slice_type = = B &&      cu_skip_flag[ x0 ][ y0 ] = = 0 && cbWidth >= 8 && cbHeight >= 8 &&      cbWidth < ( 8 * cbHeight) && cbHeight < ( 8 * cbWidth ) &&      cbWidth < 128 && cbHeight < 128 )      ciip_flag[ x0 ][ y0 ] ae(v)     if( ciip_flag[ x0 ][ y0 ] && MaxNumMergeCand > 1 )      merge_idx[ x0 ][ y0 ] ae(v)     if( !ciip_flag[ x0 ][ y0 ] ) {      merge_gpm_partition_idx[ x0 ][ y0 ] ae(v)      merge_gpm_idx0[ x0 ][ y0 ] ae(v)      if( MaxNumGpmMergeCand > 2 )       merge_gpm_idxl[ x0 ][ y0 ] ae(v)     }    }   }  } }

With respect to Table 1, JVET-S2001 provides the following semantics:

merge_idx[x0][y0] specifies the merging candidate index of the merging candidate list where x0, y0 specify the location (x0, y0) of the top-left luma sample of the considered coding block relative to the top-left luma sample of the picture. When merge_idx[x0][y0] is not present, it is inferred as follows:

-   -   If mmvd_merge_flag[x0][y0] is equal to 1, merge_idx[x0][y0] is         inferred to be equal to mmvd_cand_flag[x0][y0].     -   Otherwise (mmvd_merge_flag[x0][y0] is equal to 0),         merge_idx[x0][y0] is inferred to be equal to 0.         merge_subblock_flag[x0][y0] specifies whether the subblock-based         inter prediction parameters for the current coding unit are         inferred from neighbouring blocks. The array indices x0, y0         specify the location (x0, y0) of the top-left luma sample of the         considered coding block relative to the top-left luma sample of         the picture. When merge_subblock_flag[x0][y0] is not present, it         is inferred to be equal to 0.

merge_subblock_idx[x0][y0] specifies the merging candidate index of the subblock-based merging candidate list where x0, y0 specify the location (x0, y0) of the top-left luma sample of the considered coding block relative to the top-left luma sample of the picture.

When merge_subblock_idx[x0][y0] is not present, it is inferred to be equal to 0. regular_merge_flag[x0][y0] equal to 1 specifies that regular_merge mode or merge mode with motion vector difference is used to generate the inter prediction parameters of the current coding unit. regular_merge_flag[x0][y0] equal to 0 specifies that neither the regular_merge mode nor the merge mode with motion vector difference is used to generate the inter prediction parameters of the current coding unit. The array indices x0, y0 specify the location (x0, y0) of the top-left luma sample of the considered coding block relative to the top-left luma sample of the picture. When regular_merge_flag[x0][y0] is not present, it is inferred to be equal to general_merge_flag[x0][y0] && !merge_subblock_flag[x0][y0]. mmvd_merge_flag[x0][y0] equal to 1 specifies that merge mode with motion vector difference is used to generate the inter prediction parameters of the current coding unit. mmvd_merge_flag[x0][y0] equal to 0 specifies that merge mode with motion vector difference is not used to generate the inter prediction parameters. The array indices x0, y0 specify the location (x0, y0) of the top-left luma sample of the considered coding block relative to the top-left luma sample of the picture. When mmvd_merge_flag[x0][y0] is not present, it is inferred to be equal to 0. mmvd_cand_flag[x0][y0] specifies whether the first (0) or the second (1) candidate in the merging candidate list is used with the motion vector difference derived from mmvd_distance_idx[x0][y0] and mmvd_direction_idx[x0][y0]. The array indices x0, y0 specify the location (x0, y0) of the top-left luma sample of the considered coding block relative to the top-left luma sample of the picture. When mmvd_cand_flag[x0][y0] is not present, it is inferred to be equal to 0. mmvd_distance_idx[x0][y0] specifies the index used to derive MmvdDistance[x0][y0] as specified in Table 2. The array indices x0, y0 specify the location (x0, y0) of the top-left luma sample of the considered coding block relative to the top-left luma sample of the picture.

TABLE 2 mmvd_distance_idx MmvdDistance [x0][y0] [x0][y0] ph_mmvd_fullpel_only_flag = = 0 ph_mmvd_fullpel_only_flag = = 1 0 1 4 1 2 8 2 4 16 3 8 32 4 16 64 5 32 128 6 64 256 7 128 512 mmvd_direction_idx[x0][y0] specifies index used to derive MmvdSign[x0][y0] as specified in Table 3. The array indices x0, y0 specify the location (x0, y0) of the top-left luma sample of the considered coding block relative to the top-left luma sample of the picture.

TABLE 3 mmvd_direction_idx MmvdSign MmvdSign [x0][y0] [x0][y0][0] [x0][y0][1] 0 +1 0 1 −1 0 2 0 +1 3 0 −1 Both components of the merge plus MVD offset MmvdOffset[x0][y0] are derived as follows:

MmvdOffset[x0][y0][0]=(MmvdDistance[x0][y0]<<2)*MmvdSign[x0][y0][0]

MmvdOffset[x0][y0][1]=(MmvdDistance[x0][y0]<<2)*MmvdSign[x0][y0][1]

ciip_flag[x0][y0] specifies whether the combined inter-picture merge and intra-picture prediction is applied for the current coding unit. The array indices x0, y0 specify the location (x0, y0) of the top-left luma sample of the considered coding block relative to the top-left luma sample of the picture. When ciip_flag[x0][y0] is not present, it is inferred as follows:

If all the following conditions are true, ciip_flag[x0][y0] is inferred to be equal to 1:

-   -   sps_ciip_enabled_flag is equal to 1.     -   general_merge_flag[x0][y0] is equal to 1.     -   merge_subblock_flag[x0][y0] is equal to 0.     -   regular_merge_flag[x0][y0] is equal to 0.     -   cu_skip_flag[x0][y0] is equal to 0.     -   cbWidth is less than 128.     -   cbHeight is less than 128.     -   cbWidth*cbHeight is greater than or equal to 64.

Otherwise, ciip_flag[x0][y0] is inferred to be equal to 0.

When ciip_flag[x0][y0] is equal to 1, the variable IntraPredModeY[x][y] with x=x0.. x0+cbWidth−1 and y=y0.. y0+cbHeight−1 is set to be equal to INTRA_PLANAR. The variable MergeGpmFlag[x0][y0], which specifies whether geometric partitioning based motion compensation is used to generate the prediction samples of the current coding unit, when decoding a B slice, is derived as follows:

If all the following conditions are true, MergeGpmFlag[x0][y0] is set equal to 1:

-   -   sps_gpm_enabled_flag is equal to 1.     -   sh_slice_type is equal to B.     -   general_merge_flag[x0][y0] is equal to 1.     -   cbWidth is greater than or equal to 8.     -   cbHeight is greater than or equal to 8.     -   cbWidth is less than 8*cbHeight.     -   cbHeight is less than 8*cbWidth.     -   regular_merge_flag[x0][y0] is equal to 0.     -   merge_subblock_flag[x0][y0] is equal to 0.     -   ciip_flag[x0][y0] is equal to 0.

Otherwise, MergeGpmFlag[x0][y0] is set equal to 0.

merge_gpm_partition_idx[x0][y0] specifies the partitioning shape of the geometric partitioning merge mode. The array indices x0, y0 specify the location (x0, y0) of the top-left luma sample of the considered coding block relative to the top-left luma sample of the picture. When merge_gpm_partition_idx[x0][y0] is not present, it is inferred to be equal to 0. merge_gpm_idx0[x0][y0] specifies the first merging candidate index of the geometric partitioning based motion compensation candidate list where x0, y0 specify the location (x0, y0) of the top-left luma sample of the considered coding block relative to the top-left luma sample of the picture. When merge_gpm_idx0[x0][y0] is not present, it is inferred to be equal to 0. merge_gpm_idxl[x0][y0] specifies the second merging candidate index of the geometric partitioning based motion compensation candidate list where x0, y0 specify the location (x0, y0) of the top-left luma sample of the considered coding block relative to the top-left luma sample of the picture. When merge_gpm_idxl[x0][y0] is not present, it is inferred to be equal to 0.

As provided in the semantics above, when mmvd_merge_flag is equal to 1 merge mode with motion vector difference is used to generate the inter prediction parameters of the current coding unit. JVET-S2001 provides the following derivation process for luma motion vectors for merge mode:

This process is only invoked when general_merge_flag[xCb][yCb] is equal to 1, where (xCb, yCb) specify the top-left sample of the current luma coding block relative to the top-left luma sample of the current picture. Inputs to this process are:

-   -   a luma location (xCb, yCb) of the top-left sample of the current         luma coding block relative to the top-left luma sample of the         current picture,     -   a variable cbWidth specifying the width of the current coding         block in luma samples,     -   a variable cbHeight specifying the height of the current coding         block in luma samples.         Outputs of this process are:     -   the luma motion vectors in 1/16 fractional-sample accuracy         mvL0[0][0] and mvL1[0][0],     -   the reference indices refldxL0 and refldxL1,     -   the prediction list utilization flags predFlagL0[0][0] and         predFlagL1[0][0],     -   the half sample interpolation filter index hpe1lfldx,     -   the bi-prediction weight index bcwIdx.     -   the merging candidate list mergeCandList.         The bi-prediction weight index bcwIdx is set equal to 0.         The motion vectors mvL0[0][0] and mvL1 [0][0], the reference         indices refldxL0 and refldxL1 and the prediction utilization         flags predFlagL0[0][0] and predFlagL1[0][0] are derived by the         following ordered steps:     -   1. The derivation process for spatial merging candidates from         neighbouring coding units as specified below is invoked with the         luma coding block location (xCb, yCb), the luma coding block         width cbWidth, and the luma coding block height cbHeight as         inputs, and the output being the availability flags         availableFlagA₀, availableFlagA₁, availableFlagB₀,         availableFlagB₁ and availableFlagB₂, the reference indices         refldxLXA₀, refldxLXA₁, refldxLXB₀, refldxLXB₁ and refldxLXB₂,         the prediction list utilization flags predFlagLXA₀,         predFlagLXA₁, predFlagLXB₀, predFlagLXB₁ and predFlagLXB₂, and         the motion vectors mvLXA₀, mvLXA₁, mvLXB₀, mvLXB₁ and mvLXB₂,         with X being 0 or 1, the half sample interpolation filter         indices hpellfldxA₀, hpelIfIdxA₁, hpellfldxB₀, hpellfldxB₁,         hpellfldxB₂, and the bi-prediction weight indices bcwldxA₀,         bcwldxA₁, bcwldxB₀, bcwIdxB₁, bcwIdxB₂.     -   2. The reference indices, refldxLXCol, with X being 0 or 1, and         the bi-prediction weight index bcwldxCo1 for the temporal         merging candidate Co1 are set equal to 0 and hpelIfIdxCo1 is set         equal to 0.     -   3. The derivation process for temporal luma motion vector         prediction as specified is invoked with the luma location (xCb,         yCb), the luma coding block width cbWidth, the luma coding block         height cbHeight and the variable refldxL0Co1 as inputs, and the         output being the availability flag availableFlagL0Co1 and the         temporal motion vector mvL0Co1. The variables availableFlagCo1,         predFlagL0Co1 and predFlagL1Co1 are derived as follows:

availableFlagCo1=availableFlagL0Co1

predFlagL0Co1=availableFlagL0Co1

predFlagL1Co1=0

-   -   4. When sh_slice_type is equal to B, the derivation process for         temporal luma motion vector prediction as specified is invoked         with the luma location (xCb, yCb), the luma coding block width         cbWidth, the luma coding block height cbHeight and the variable         refldxL1Co1 as inputs, and the output being the availability         flag availableFlagL1Co1 and the temporal motion vector mvL1Co1.         The variables availableFlagCo1 and predFlagL1Co1 are derived as         follows:

availableFlagCo1=availableFlagL0Co1∥availableFlagL1Co1

predFlagL1Co1=availableFlagL1Co1

-   -   5. The merging candidate list, mergeCandList, is constructed as         follows:     -   i=0     -   if(availableFlagB₁)         -   mergeCandList[i++]=B₁     -   if(availableFlagA₁)         -   mergeCandList[i++]=A₁     -   if(availableFlagB₀)         -   mergeCandList[i++]=B₀     -   if(availableFlagA₀)         -   mergeCandList[i++]=A₀     -   if(availableFlagB₂)         -   mergeCandList[i++]=B₂     -   if(availableFlagCo1)         -   mergeCandList[i++]=Co1     -   6. The variable numCurrMergeCand and numOrigMergeCand are set         equal to the number of merging candidates in the mergeCandList.     -   7. When numCurrMergeCand is less than (MaxNumMergeCand−1) and         NumHmvpCand is greater than 0, the following applies:         -   The derivation process of history-based merging candidates             as specified is invoked with mergeCandList and             numCurrMergeCand as inputs, and modified mergeCandList and             numCurrMergeCand as outputs.         -   numOrigMergeCand is set equal to numCurrMergeCand.     -   8. When numCurrMergeCand is less than MaxNumMergeCand and         greater than 1, the following applies:         -   The derivation process for pairwise average merging             candidate as specified is invoked with mergeCandList, the             reference indices refldxL0N and refldxL1N, the prediction             list utilization flags predFlagL0N and predFlagL1N, the             motion vectors mvL0N and mvL1N, and the half sample             interpolation filter index hpellfldxN of every candidate N             in mergeCandList, and numCurrMergeCand as inputs, and the             output is assigned to mergeCandList, numCurrMergeCand, the             reference indices refldxL0avgCand and refldxL1avgCand, the             prediction list utilization flags predFlagLOavgCand and             predFlagLlavgCand, the motion vectors mvL0avgCand and             mvLlavgCand, and the half-sample interpolation filter index             hpellfldxavgCand of candidate avgCand being added into             mergeCandList. The bi-prediction weight index bcwldx of             candidate avgCand being added into mergeCandList is set             equal to 0.         -   numOrigMergeCand is set equal to numCurrMergeCand.     -   9. The derivation process for zero motion vector merging         candidates as specified is invoked with the mergeCandList, the         reference indices refldxL0N and refldxL1N, the prediction list         utilization flags predFlagL0N and predFlagL1N, the motion         vectors mvL0N and mvL1N of every candidate N in mergeCandList         and numCurrMergeCand as inputs, and the output is assigned to         mergeCandList, numCurrMergeCand, the reference indices         refldxL0zeroCand_(m) and refldxL1 zeroCand_(m), the prediction         list utilization flags predFlagLOzeroCand_(m) and predFlagL1         zeroCand_(m) and the motion vectors mvL0zeroCand_(m) and         mvL1zeroCand_(m) of every new candidate zeroCand_(m) being added         into mergeCandList. The half sample interploation filter index         hpellfldx of every new candidate zeroCand_(m) being added into         mergeCandList is set equal to 0. The bi-prediction weight index         bcwldx of every new candidate zeroCand_(m) being added into         mergeCandList is set equal to 0. The number of candidates being         added, numZeroMergeCand, is set equal to         (numCurrMergeCand−numOrigMergeCand). When numZeroMergeCand is         greater than 0, m ranges from 0 to numZeroMergeCand−1,         inclusive.     -   10. The following assignments are made with N being the         candidate at position merge_idx[xCb][yCb] in the merging         candidate list mergeCandList         (N=mergeCandList[merge_idx[xCb][yCb] ]) and X being replaced by         0 or 1:         -   refldxLX=refldxLXN         -   predFlagLX[0][0]=predFlagLXN         -   mvLX[0][0][0]=mvLXN[0]         -   mvLX[ 0][ 0][1]=mvLXN[1]         -   hpellfldx=hpellfldxN         -   bcwldx=bcwldxN     -   11. When mmvd_merge_flag[xCb][yCb] is equal to 1, the following         applies:         -   The derivation process for merge motion vector difference as             specified below is invoked with the luma location (xCb,             yCb), the reference indices refldxL0, refldxL1 and the             prediction list utilization flags predFlagL0[0][0] and             predFlagL1[0][0] as inputs, and the motion vector             differences mMvdL0 and mMvdL1 as outputs.         -   The motion vector difference mMvdLX is added to the merge             motion vectors mvLX for X being 0 and 1 as follows:             -   mvLX[0][0][0]+=mMvdLX[0]             -   mvLX[ 0][ 0][1]+=mMvdLX[1]             -   mvLX[ 0][ 0][ 0]=Clip3(−2¹⁷, 2¹⁷−1, mvLX[0][0][0])             -   mvLX[0][0] [ 1]=Clip3(−2¹⁷, 2¹⁷−1, mvLX[0][0][1])

Derivation process for spatial merging candidates

Inputs to this process are:

-   -   a luma location (xCb, yCb) of the top-left sample of the current         luma coding block relative to the top-left luma sample of the         current picture,     -   a variable cbWidth specifying the width of the current coding         block in luma samples,     -   a variable cbHeight specifying the height of the current coding         block in luma samples.

Outputs of this process are as follows, with X being 0 or 1:

-   -   the availability flags availableFlagA₀, availableFlagA₁,         availableFlagB₀, availableFlagB₁ and availableFlagB₂ of the         neighbouring coding units,     -   the reference indices refldxLXA₀, refldxLXA₁, refldxLXB₀,         refldxLXB₁ and refldxLXB₂ of the neighbouring coding units,     -   the prediction list utilization flags predFlagLXA₀,         predFlagLXA₁, predFlagLXB₀, predFlagLXB₁ and predFlagLXB₂ of the         neighbouring coding units,     -   the motion vectors in 1/16 fractional-sample accuracy mvLXA₀,         mvLXA₁, mvLXB₀, mvLXB₁ and mvLXB₂ of the neighbouring coding         units,     -   the half sample interpolation filter indices hpelIfIdxA₀,         hpelIfIdxA₁, hpelIfIdxB₀, hpelIfIdxB₁, and hpellfldxB₂,     -   the bi-prediction weight indices bcwIdxA₀, bcwIdxA₁, bcwIdxB₀,         bcwIdxB₁, and bcwIdxB₂.

For the derivation of availableFlagB₁, refldxLXB₁, predFlagLXB₁, mvLXB₁, hpelIfIdxB₁ and bcwIdxB₁ the following applies:

-   -   The luma location (xNbB₁, yNbB₁) inside the neighbouring luma         coding block is set equal to (xCb+cbWidth−1, yCb−1).     -   The derivation process for neighbouring block availability as         specified is invoked with the current luma location (xCurr,         yCurr) set equal to (xCb, yCb), the neighbouring luma location         (xNbB₁, yNbB₁), checkPredModeY set equal to TRUE, and cIdx set         equal to 0 as inputs, and the output is assigned to the block         availability flag availableB₁.     -   When xCb»Log2ParMrgLevel is equal to xNbB₁»Log2ParMrgLevel and         yCb»Log2ParMrgLevel is equal to yNbB₁»Log2ParMrgLevel,         availableB₁ is set equal to FALSE.     -   The variables availableFlagB₁, refldxLXB₁, predFlagLXB₁, mvLXB₁,         hpelIfIdxB₁ and bcwIdxB₁ are derived as follows:     -   If availableB₁ is equal to FALSE, availableFlagB₁ is set equal         to 0, both components of mvLXB₁ are set equal to 0, refldxLXB₁         is set equal to −1 and predFlagLXB₁ is set equal to 0, with X         being 0 or 1, hpelIfIdxB₁ is set equal to 0, and bcwIdxB₁ is set         equal to 0.     -   Otherwise, availableFlagB₁ is set equal to 1 and the following         assignments are made:         -   mvLXB₁=MvLX[xNbB₁][yNbB₁]         -   refldxLXB₁=RefldxLX[xNbB₁][yNbB₁]         -   predFlagLXB₁=PredFlagLX[xNbB₁][yNbB₁]         -   hpelIfIdxB₁=Hpellfldx[xNbB₁][yNbB₁]         -   bcwIdxB₁=Bcwldx[xNbB₁][yNbB₁]

For the derivation of availableFlagA₁, refldxLXA₁, predFlagLXA₁, mvLXA₁, hpellfldxA₁ and bcwldxA₁ the following applies:

-   -   The luma location (xNbA₁, yNbA₁) inside the neighbouring luma         coding block is set equal to (xCb−1, yCb+cbHeight−1).     -   The derivation process for neighbouring block availability as         specified is invoked with the current luma location (xCurr,         yCurr) set equal to (xCb, yCb). the neighbouring luma location         (xNbA₁, yNbA₁), checkPredModeY set equal to TRUE, and cIdx set         equal to 0 as inputs, and the output is assigned to the block         availability flag availableA₁.     -   When xCb»Log2ParMrgLevel is equal to xNbA₁»Log2ParMrgLevel and         yCb»Log2ParMrgLevel is equal to yNbA₁»Log2ParMrgLevel,         availableA₁ is set equal to FALSE.     -   The variables availableFlagA₁, refldxLXA₁, predFlagLXA₁, mvLXA₁,         hpellfldxA₁ and bcwIdxA₁ are derived as follows:         -   If one or more of the following conditions are true,             availableFlagA₁ is set equal to 0, both components of mvLXA₁             are set equal to 0, refldxLXA₁ is set equal to −1 and             predFlagLXA₁ is set equal to 0, with X being 0 or 1,             hpellfldxA₁ is set equal to 0, and bcwldxA₁ is set equal to             0:             -   availableA₁ is equal to FALSE.             -   availableB₁ is equal to TRUE and the luma locations                 (xNbA₁, yNbA₁) and (xNbB₁, yNbB₁) have the same motion                 vectors and the same reference indices.         -   Otherwise, availableFlagA₁ is set equal to 1 and the             following assignments are made:             -   mvLXA₁=MvLX[xNbA₁][yNbA₁]             -   refldxLXA₁=RefldxLX[xNbA₁][yNbA₁]             -   predFlagLXA₁=PredFlagLX[xNbA₁][yNbA₁]             -   hpellfldxA₁=Hpellfldx[xNbA₁][yNbA₁]             -   bcwldxA₁=Bcwldx[xNbA₁][yNbA₁]

For the derivation of availableFlagB₀, refldxLXB₀, predFlagLXB₀, mvLXB₀, hpellfldxB₀ and bcwldxB₀ the following applies:

-   -   The luma location (xNbB₀, yNbB₀) inside the neighbouring luma         coding block is set equal to (xCb+cbWidth, yCb−1).     -   The derivation process for neighbouring block availability as         specified is invoked with the current luma location (xCurr,         yCurr) set equal to (xCb, yCb), the neighbouring luma location         (xNbB₀, yNbB₀), checkPredModeY set equal to TRUE, and cIdx set         equal to 0 as inputs, and the output is assigned to the block         availability flag availableB₀.     -   When xCb»Log2ParMrgLevel is equal to xNbB₀»Log2ParMrgLevel and         yCb»Log2ParMrgLevel is equal to yNbB₀»Log2ParMrgLevel,         availableB₀ is set equal to FALSE.     -   The variables availableFlagB₀, refldxLXB₀, predFlagLXB₀, mvLXB₀,         hpellfldxB₀ and bcwldxB₀ are derived as follows:     -   If one or more of the following conditions are true,         availableFlagB₀ is set equal to 0, both components of mvLXB₀ are         set equal to 0, refldxLXB₀ is set equal to −1 and predFlagLXB₀         is set equal to 0, with X being 0 or 1, hpellfldxB₀ is set equal         to 0, and bcwIdxB₀ is set equal to 0:         -   availableB₀ is equal to FALSE.         -   availableB₁ is equal to TRUE and the luma locations (xNbB₁,             yNbB₁) and (xNbB₀, yNbB₀) have the same motion vectors and             the same reference indices.     -   Otherwise, availableFlagB₀ is set equal to 1 and the following         assignments are made:         -   mvLXB₀=MvLX[xNbB₀][yNbB₀]         -   refldxLXB₀=RefldxLX[xNbB₀][yNbB₀]         -   predFlagLXB₀=PredFlagLX[xNbB₀][yNbB₀]         -   hpellfldxB₀=Hpellfldx[xNbB₀][yNbB₀]         -   bcwIdxB₀=Bcwldx[xNbB₀][yNbB₀]

For the derivation of availableFlagA₀, refldxLXA₀, predFlagLXA₀, mvLXA₀, hpellfldxA₀ and bcwldxA₀ the following applies:

-   -   The luma location (xNbA₀, yNbA₀) inside the neighbouring luma         coding block is set equal to (xCb−1, yCb+cbHeight).     -   The derivation process for neighbouring block availability as         specified is invoked with the current luma location (xCurr,         yCurr) set equal to (xCb, yCb). the neighbouring luma location         (xNbA₀, yNbA₀), checkPredModeY set equal to TRUE, and cIdx set         equal to 0 as inputs, and the output is assigned to the block         availability flag availableA₀.     -   When xCb»Log2ParMrgLevel is equal to xNbA₀»Log2ParMrgLevel and         yCb»Log2ParMrgLevel is equal to yNbA₀»Log2ParMrgLevel,         availableA₀ is set equal to FALSE.     -   The variables availableFlagA₀, refldxLXA₀, predFlagLXA₀, mvLXA₀,         hpellfldxA₀ and bcwldxA₀ are derived as follows:         -   If one or more of the following conditions are true,             availableFlagA₀ is set equal to 0, both components of mvLXA₀             are set equal to 0, refldxLXA₀ is set equal to −1 and             predFlagLXA₀ is set equal to 0, with X being 0 or 1,             hpellfldxA₀ is set equal to 0, and bcwldxA₀ is set equal to             0:             -   availableA₀ is equal to FALSE.             -   availableA₁ is equal to TRUE and the luma locations                 (xNbA₁, yNbA₁) and (xNbA₀, yNbA₀) have the same motion                 vectors and the same reference indices.         -   Otherwise, availableFlagA₀ is set equal to 1 and the             following assignments are made:             -   mvLXA₀=MvLX[xNbA₀][yNbA₀]             -   refldxLXA₀=RefldxLX[xNbA₀][yNbA₀]             -   predFlagLXA₀=PredFlagLX[xNbA₀][yNbA₀]             -   hpellfldxA₀=Hpellfldx[xNbA₀][yNbA₀]             -   bcwldxA₀=Bcwldx[xNbA₀][yNbA₀]

For the derivation of availableFlagB₂, refldxLXB₂, predFlagLXB₂, mvLXB₂, hpellfldxB₂ and bcwIdxB₂ the following applies:

-   -   The luma location (xNbB₂, yNbB₂) inside the neighbouring luma         coding block is set equal to (xCb−1, yCb−1).     -   The derivation process for neighbouring block availability as         specified is invoked with the current luma location (xCurr,         yCurr) set equal to (xCb, yCb), the neighbouring luma location         (xNbB₂, yNbB₂), checkPredModeY set equal to TRUE, and cIdx set         equal to 0 as inputs, and the output is assigned to the block         availability flag availableB₂.     -   When xCb»Log2ParMrgLevel is equal to xNbB₂»Log2ParMrgLevel and         yCb»Log2ParMrgLevel is equal to yNbB₂»Log2ParMrgLevel,         availableB₂ is set equal to FALSE.     -   The variables availableFlagB₂, refldxLXB₂, predFlagLXB₂, mvLXB₂,         hpellfldxB₂ and bcwIdxB₂ are derived as follows:         -   If one or more of the following conditions are true,             availableFlagB₂ is set equal to 0, both components of mvLXB₂             are set equal to 0, refldxLXB₂ is set equal to −1 and             predFlagLXB₂ is set equal to 0, with X being 0 or 1,             hpellfldxB₂ is set equal to 0, and bcwIdxB₂ is set equal to             0:             -   availableB₂ is equal to FALSE.             -   availableA₁ is equal to TRUE and the luma locations                 (xNbA₁, yNbA₁) and (xNbB₂, yNbB₂) have the same motion                 vectors and the same reference indices.             -   availableB₁ is equal to TRUE and the luma locations                 (xNbB₁, yNbB₁) and (xNbB₂, yNbB₂) have the same motion                 vectors and the same reference indices.             -   availableFlagA₀+availableFlagA₁+availableFlagB₀+availableFlagB₁                 is equal to 4.         -   Otherwise, availableFlagB₂ is set equal to 1 and the             following assignments are made:             -   mvLXB₂=MvLX[xNbB₂][yNbB₂]             -   refldxLXB₂=RefldxLX[xNbB₂][yNbB₂]             -   predFlagLXB₂=PredFlagLX[xNbB₂][yNbB₂]             -   hpelIfIdxB₂=Hpellfldx[xNbB₂][yNbB₂]             -   bcwIdxB₂=Bcwldx[xNbB₂][yNbB₂]

Derivation Process for Merge Motion Vector Difference

Inputs to this process are:

-   -   a luma location (xCb, yCb) of the top-left sample of the current         luma coding block relative to the top-left luma sample of the         current picture,     -   reference indices refldxL0 and refldxL1,     -   prediction list utilization flags predFlagL0 and predFlagL1.

Outputs of this process are the luma merge motion vector differences in 1/16 fractional-sample accuracy mMvdL0 and mMvdL1.

The variable currPic specifies the current picture.

The luma merge motion vector differences mMvdL0 and mMvdL1 are derived as follows:

-   -   If both predFlagL0 and predFlagL1 are equal to 1, the following         applies:         -   currPocDiffL0=DiffPicOrderCnt(currPic,             RefPicList[0][refldxL0])         -   currPocDiffL1=DiffPicOrderCnt(currPic,             RefPicList[1][refldxL1])     -   If currPocDiffL0 is equal to currPocDiffL1, the following         applies:         -   mMvdL0[0]=MmvdOffset[xCb][yCb][0]         -   mMvdL0[1]=MmvdOffset[xCb][yCb][1]         -   mMvdL1[0]=MmvdOffset[xCb][yCb][0]         -   mMvdL1[1]=MmvdOffset[xCb][yCb][1]     -   Otherwise, if Abs(currPocDiffL0) is greater than or equal to         Abs(currPocDiffL1), the following applies:         -   mMvdL0[0]=MmvdOffset[xCb][yCb][0]         -   mMvdL0[1]=MmvdOffset[xCb][yCb][1]     -   If RefPicList[0][refldxL0] is not an LTRP and         RefPicList[1][refldxL1] is not an LTRP, the following applies:         -   td=Clip3(−128, 127, currPocDiffL0)         -   tb=Clip3(−128, 127, currPocDiffL1)         -   tx=(16384+(Abs(td)»1))/td         -   distScaleFactor=Clip3(−4096, 4095, (tb*tx+32)»6)         -   mMvdL1[0]=Clip3(−2¹⁷, 2¹⁷−1,             (distScaleFactor*mMvdL0[0]+128−(distScaleFactor*mMvdL0[0]>=0))»8)         -   mMvdL1[1]=Clip3(−2¹⁷, 2¹⁷−1,             (distScaleFactor*mMvdL0[1]+128−(distScaleFactor*mMvdL0[1]>=0))»8)     -   Otherwise, the following applies:         -   mMvdL1[0]=Sign(currPocDiffL0)==Sign(currPocDiffL1)?             -   mMvdL0[0]:−mMvdL0[0]         -   mMvdL1[1]=Sign(currPocDiffL0)==Sign(currPocDiffL1)?             -   mMvdL0[1]:−mMvdL0[1]     -   Otherwise (Abs(currPocDiffL0) is less than Abs(currPocDiffL1)),         the following applies:         -   mMvdL1[0]=MmvdOffset[xCb][yCb][0]         -   mMvdL1[1]=MmvdOffset[xCb][yCb][1]     -   If RefPicList[0][refldxL0] is not an LTRP and         RefPicList[1][refldxL1] is not an LTRP, the following applies:         -   td=Clip3(−128, 127, currPocDiffL1)         -   tb=Clip3(−128, 127, currPocDiffL0)         -   tx=(16384+(Abs(td)» 1))/td         -   distScaleFactor=Clip3(−4096, 4095, (tb*tx+32)»6)         -   mMvdL0[0]=Clip3(−2¹⁷, 2¹⁷−1,             (distScaleFactor*mMvdL1[0]+128−(distScaleFactor*mMvdL1[0]>=0))»8)             mMvdL0[1]=Clip3(−2¹⁷, 2¹⁷−1,             (distScaleFactor*mMvdL1[1]+128−(distScaleFactor*mMvdL1[1]>=0))»8))     -   Otherwise, the following applies:         -   mMvdL0[0]=Sign(currPocDiffL0)==Sign(currPocDiffL1)?             -   mMvdL1[0]:−mMvdL1[0]         -   mMvdL0[1]=Sign(currPocDiffL0)==Sign(currPocDiffL1)?             -   mMvdL1[1]:−mMvdL1[1]     -   Otherwise (predFlagL0 or predFlagL1 are equal to 1), the         following applies for X being 0 and 1:         -   mMvdLX[0]=(predFlagLX==1)? MmvdOffset[xCb][yCb][0]:0         -   mMvdLX[1]=(predFlagLX==1)? MmvdOffset[xCb][yCb][1]:0

It should be noted that LTRP refers to a long term reference picture and JVET-S2001 provides the following decoding process for reference picture marking:

This process is invoked once per picture, after decoding of a slice header and the decoding process for reference picture list construction for the slice as specified, but prior to the decoding of the slice data. This process may result in one or more reference pictures in the DPB being marked as “unused for reference” or “used for long-term reference”. A decoded picture in the DPB can be marked as “unused for reference”, “used for short-term reference” or “used for long-term reference”, but only one among these three at any given moment during the operation of the decoding process. Assigning one of these markings to a picture implicitly removes another of these markings when applicable. When a picture is referred to as being marked as “used for reference”, this collectively refers to the picture being marked as “used for short-term reference” or “used for long-term reference” (but not both).

STRPs (short-term reference pictures) and ILRPs (inter-layer reference pictures) are identified by their nuh_layer_id and PicOrderCntVal values. LTRPs are identified by their nuh_layer_id values and by the Log2(MaxPicOrderCntLsb) LSBs of their PicOrderCntVal values or their PicOrderCntVal values.

If the current picture is a CLVSS picture, all reference pictures currently in the DPB (if any) with the same nuh_layer_id as the current picture are marked as “unused for reference”. Otherwise, the following applies:

-   -   For each LTRP entry in RefPicList[0] or RefPicList[1], when the         picture is an STRP with the same nuh_layer_id as the current         picture, the picture is marked as “used for long-term         reference”.     -   Each reference picture with the same nuh_layer_id as the current         picture in the DPB that is not referred to by any entry in         RefPicList[0] or RefPicList[1] is marked as “unused for         reference”.

For each ILRP entry in RefPicList[0] or RefPicList[1], the picture is marked as “used for long-term reference”

It should be noted that JVET-S2001 provides the following definition for an ILRP:

inter-layer reference picture (ILRP): A picture in the same access unit (AU) with the current picture, with nuh_layer_id less than the nuh_layer_id of the current picture, and is marked as “used for long-term reference”.

Where JVET-S2001 provides the following semantics for nuh_layer_id:

nuh_layer_id specifies the identifier of the layer to which a video coding layer (VCL) NAL unit belongs or the identifier of a layer to which a non-VCL NAL unit applies. The value of nuh_layer_id shall be in the range of 0 to 55, inclusive. Other values for nuh_layer_id are reserved for future use by ITU-T I ISO/IEC.

The value of nuh_layer_id shall be the same for all VCL NAL units of a coded picture. The value of nuh_layer_id of a coded picture or a Picture Unit (PU) is the value of the nuh_layer_id of the VCL NAL units of the coded picture or the PU.

When nal_unit_type is equal to PH_NUT, or FD_NUT, nuh_layer_id shall be equal to the nuh_layer_id of associated VCL NAL unit.

When nal_unit_type is equal to EOS_NUT, nuh_layer_id shall be equal to one of the nuh_layer_id values of the layers present in the CVS.

-   -   NOTE— The value of nuh_layer_id for DCI, OPI, VPS, AUD, and EOB         NAL units is not constrained.

It should be noted that the derivation process for merge motion vector difference in JVET-S2001 provides a scaling function for scaling the merge motion vector differences (MMVD) to account for the distance in time between reference pictures and the current picture when two reference pictures are used to predict a block. However, the manner in which JVET-S2001 handles the case where one of two reference pictures and the current picture have the same picture order count (POC) is less than ideal as it results in a scaling value of −1. Scaling a motion vector difference by a value of −1 to account for the distance in time between reference pictures and the current picture does not make sense when a first reference picture and the current picture have the same POC, and a second reference picture and the current picture do not have the same POC.

As described above, intra prediction data or inter prediction data is used to produce reference sample values for a block of sample values. The difference between sample values included in a current PB, or another type of picture area structure, and associated reference samples (e.g., those generated using a prediction) may be referred to as residual data. Residual data may include respective arrays of difference values corresponding to each component of video data. Residual data may be in the pixel domain. A transform, such as, a discrete cosine transform (DCT), a discrete sine transform (DST), an integer transform, a wavelet transform, or a conceptually similar transform, may be applied to an array of difference values to generate transform coefficients. It should be noted that in ITU-T H.265 and JVET-52001, a CU is associated with a transform tree structure having its root at the CU level. The transform tree is partitioned into one or more transform units (TUs). That is, an array of difference values may be partitioned for purposes of generating transform coefficients (e.g., four 8×8 transforms may be applied to a 16×16 array of residual values). For each component of video data, such sub-divisions of difference values may be referred to as Transform Blocks (TBs). It should be noted that in some cases, a core transform and subsequent secondary transforms may be applied (in the video encoder) to generate transform coefficients. For a video decoder, the order of transforms is reversed.

A quantization process may be performed on transform coefficients or residual sample values directly (e.g., in the case, of palette coding quantization). Quantization approximates transform coefficients by amplitudes restricted to a set of specified values. Quantization essentially scales transform coefficients in order to vary the amount of data required to represent a group of transform coefficients. Quantization may include division of transform coefficients (or values resulting from the addition of an offset value to transform coefficients) by a quantization scaling factor and any associated rounding functions (e.g., rounding to the nearest integer). Quantized transform coefficients may be referred to as coefficient level values. Inverse quantization (or “dequantization”) may include multiplication of coefficient level values by the quantization scaling factor, and any reciprocal rounding or offset addition operations. It should be noted that as used herein the term quantization process in some instances may refer to division by a scaling factor to generate level values and multiplication by a scaling factor to recover transform coefficients in some instances. That is, a quantization process may refer to quantization in some cases and inverse quantization in some cases. Further, it should be noted that although in some of the examples below quantization processes are described with respect to arithmetic operations associated with decimal notation, such descriptions are for illustrative purposes and should not be construed as limiting. For example, the techniques described herein may be implemented in a device using binary operations and the like. For example, multiplication and division operations described herein may be implemented using bit shifting operations and the like.

Quantized transform coefficients and syntax elements (e.g., syntax elements indicating a coding structure for a video block) may be entropy coded according to an entropy coding technique. An entropy coding process includes coding values of syntax elements using lossless data compression algorithms. Examples of entropy coding techniques include content adaptive variable length coding (CAVLC), context adaptive binary arithmetic coding (CABAC), probability interval partitioning entropy coding (PIPE), and the like. Entropy encoded quantized transform coefficients and corresponding entropy encoded syntax elements may form a compliant bitstream that can be used to reproduce video data at a video decoder. An entropy coding process, for example, CABAC, may include performing a binarization on syntax elements. Binarization refers to the process of converting a value of a syntax element into a series of one or more bits. These bits may be referred to as “bins.” Binarization may include one or a combination of the following coding techniques: fixed length coding, unary coding, truncated unary coding, truncated Rice coding, Golomb coding, k-th order exponential Golomb coding, and Golomb-Rice coding. For example, binarization may include representing the integer value of 5 for a syntax element as 00000101 using an 8-bit fixed length binarization technique or representing the integer value of 5 as 11110 using a unary coding binarization technique. As used herein each of the terms fixed length coding, unary coding, truncated unary coding, truncated Rice coding, Golomb coding, k-th order exponential Golomb coding, and Golomb-Rice coding may refer to general implementations of these techniques and/or more specific implementations of these coding techniques. For example, a Golomb-Rice coding implementation may be specifically defined according to a video coding standard. In the example of CABAC, for a particular bin, a context provides a most probable state (MPS) value for the bin (i.e., an MPS for a bin is one of 0 or 1) and a probability value of the bin being the MPS or the least probably state (LPS). For example, a context may indicate, that the MPS of a bin is 0 and the probability of the bin being 1 is 0.3. It should be noted that a context may be determined based on values of previously coded bins including bins in the current syntax element and previously coded syntax elements. For example, values of syntax elements associated with neighboring video blocks may be used to determine a context for a current bin.

As described above, video content includes video sequences comprised of a series of pictures and each picture may be divided into one or more regions. In JVET-S2001, a coded representation of a picture comprises VCL NAL units of a particular layer within an AU and contains all CTUs of the picture. For example, referring again to FIG. 2 , the coded representation of Pica is encapsulated in three coded slice NAL units (i.e., Slice® NAL unit, Slice₁ NAL unit, and Slice₂ NAL unit). It should be noted that the term video coding layer (VCL) NAL unit is used as a collective term for coded slice NAL units, i.e., VCL NAL is a collective term which includes all types of slice NAL units. As described above, and in further detail below, a NAL unit may encapsulate metadata used for decoding video data. A NAL unit encapsulating metadata used for decoding a video sequence is generally referred to as a non-VCL NAL unit. Thus, in JVET-S2001, a NAL unit may be a VCL NAL unit or a non-VCL NAL unit. It should be noted that a VCL NAL unit includes slice header data, which provides information used for decoding the particular slice. Thus, in JVET-S2001, information used for decoding video data, which may be referred to as metadata in some cases, is not limited to being included in non-VCL NAL units. JVET-52001 provides where a picture unit (PU) is a set of NAL units that are associated with each other according to a specified classification rule, are consecutive in decoding order, and contain exactly one coded picture and where an access unit (AU) is a set of PUs that belong to different layers and contain coded pictures associated with the same time for output from the DPB. JVET-S2001 further provides where a layer is a set of VCL NAL units that all have a particular value of a layer identifier and the associated non-VCL NAL units. Further, in JVET-S2001, a PU consists of zero or one PH NAL units, one coded picture, which comprises of one or more VCL NAL units, and zero or more other non-VCL NAL units. Further, in JVET-S2001, a coded video sequence (CVS) is a sequence of AUs that consists, in decoding order, of a CVSS AU, followed by zero or more AUs that are not CVSS AUs, including all subsequent AUs up to but not including any subsequent AU that is a CVSS AU, where a coded video sequence start (CVSS) AU is an AU in which there is a PU for each layer in the CVS and the coded picture in each present picture unit is a coded layer video sequence start (CLVSS) picture. In JVET-S2001, a coded layer video sequence (CLVS) is a sequence of PUs within the same layer that consists, in decoding order, of a CLVSS PU, followed by zero or more PUs that are not CLVSS PUs, including all subsequent PUs up to but not including any subsequent PU that is a CLVSS PU. This is, in JVET-S2001, a bitstream may be described as including a sequence of AUs forming one or more CVSs.

Multi-layer video coding enables a video presentation to be decoded/displayed as a presentation corresponding to a base layer of video data and decoded/displayed one or more additional presentations corresponding to enhancement layers of video data. For example, a base layer may enable a video presentation having a basic level of quality (e.g., a High Definition rendering and/or a 30 Hz frame rate) to be presented and an enhancement layer may enable a video presentation having an enhanced level of quality (e.g., an Ultra High Definition rendering and/or a 60 Hz frame rate) to be presented. An enhancement layer may be coded by referencing a base layer. That is, for example, a picture in an enhancement layer may be coded (e.g., using inter-layer prediction techniques) by referencing one or more pictures (including scaled versions thereof) in a base layer. It should be noted that layers may also be coded independent of each other. In this case, there may not be inter-layer prediction between two layers. Each NAL unit may include an identifier indicating a layer of video data the NAL unit is associated with. As described above, a sub-bitstream extraction process may be used to only decode and display a particular region of interest of a picture. Further, a sub-bitstream extraction process may be used to only decode and display a particular layer of video. Sub-bitstream extraction may refer to a process where a device receiving a compliant or conforming bitstream forms a new compliant or conforming bitstream by discarding and/or modifying data in the received bitstream. For example, sub-bitstream extraction may be used to form a new compliant or conforming bitstream corresponding to a particular representation of video (e.g., a high quality representation).

In JVET-52001, each of a video sequence, a GOP, a picture, a slice, and CTU may be associated with metadata that describes video coding properties and some types of metadata an encapsulated in non-VCL NAL units. JVET-52001 defines parameters sets that may be used to describe video data and/or video coding properties. In particular, JVET-52001 includes the following four types of parameter sets: video parameter set (VPS), sequence parameter set (SPS), picture parameter set (PPS), and adaption parameter set (APS), where a SPS applies to apply to zero or more entire CVSs, a PPS applies to zero or more entire coded pictures, a APS applies to zero or more slices, and a VPS may be optionally referenced by a SPS. A PPS applies to an individual coded picture that refers to it. In JVET-52001, parameter sets may be encapsulated as a non-VCL NAL unit and/or may be signaled as a message. JVET-52001 also includes a picture header (PH) which is encapsulated as a non-VCL NAL unit. In JVET-52001, a picture header applies to all slices of a coded picture. JVET-S2001 further enables decoding capability information (DCI) and supplemental enhancement information (SEI) messages to be signaled. In JVET-52001, DCI and SEI messages assist in processes related to decoding, display or other purposes, however, DCI and SEI messages may not be required for constructing the luma or chroma samples according to a decoding process. In JVET-52001, DCI and SEI messages may be signaled in a bitstream using non-VCL NAL units. Further, DCI and SEI messages may be conveyed by some mechanism other than by being present in the bitstream (i.e., signaled out-of-band).

As described above, when a picture is decoded it is stored to a decoded picture buffer (DPB). JVET-S2001 provides where a decoded picture buffer parameters syntax structure may be include in a VPS or SPS. Table 4 illustrates the decoded picture buffer parameters syntax structure provided in JVET-S2001.

TABLE 4 dpb_parameters( MaxSubLayersMinus1, subLayerInfoFlag ) { Descriptor  for( i = ( subLayerlnfoFlag ? 0 : MaxSubLayersMinus1 );    i <= MaxSubLayersMinus1; i++ ) {   dpb_max_dec_pic_buffering_minus1[ i ] ue(v)   dpb_max_num_reorder_pics[ i ] ue(v)   dpb_max_latency_increase_plus1[ i ] ue(v)  } }

With respect to Table 4, JVET-S2001 provides the following semantics:

The dpb_parameters( ) syntax structure provides information of DPB size, maximum picture reorder number, and maximum latency for one or more OLSs (output layer sets). When a dpb_parameters( )syntax structure is included in a VPS, the OLSs to which the dpb_parameters( )syntax structure applies are specified by the VPS. When a dpb_parameters( ) syntax structure is included in an SPS, it applies to the OLS that includes only the layer that is the lowest layer among the layers that refer to the SPS, and this lowest layer is an independent layer.

dpb_max_dec_pic_buffering_minusl[i] plus 1 specifies the maximum required size of the DPB in units of picture storage buffers when Htid is equal to i. The value of dpb_max_dec_pic_buffering_minusl [i] shall be in the range of 0 to MaxDpbSize−1, inclusive, where MaxDpbSize is as specified below. When i is greater than 0, dpb_max_dec_pic_buffering_minusl [i] shall be greater than or equal to dpb_max_dec_pic_buffering_minusl [i−1]. When dpb_max_dec_pic_buffering_minusl [i] is not present for i in the range of 0 to MaxSubLayersMinus1−1, inclusive, due to subLayerInfoFlag being equal to 0, it is inferred to be equal to dpb_max_dec_pic_buffering_minusl[MaxSubLayersMinus1].

When the specified level is not level 15.5, the value of dpb_max_dec_pic_buffering_minusl[Htid]+1 shall be less than or equal to MaxDpbSize, which is derived as follows:

if( PicSizeMaxInSamplesY <= ( MaxLumaPs >> 2 ) )  MaxDpbSize = Min( 4 * maxDpbPicBuf, 16 ) else if( PicSizeMaxInSamplesY <= ( MaxLumaPs >> 1 ) )  MaxDpbSize = Min( 2 * maxDpbPicBuf, 16 ) else if( PicSizeMaxInSamplesY <= ( ( 3 * MaxLumaPs ) >> 2 ) )  MaxDpbSize = Min( ( 4 * maxDpbPicBuf ) / 3, 16 ) else  MaxDpbSize = maxDpbPicBuf where MaxLumaPs is specified in Table 5, maxDpbPicBuf is equal to 8, and dpb_max_dec_pic_buffering_minusl [Htid] is found in or derived from the applicable dpb_parameters( ) syntax structure.

TABLE 5 Max CPB Max #  general_ Max luma size MaxCPB Max slices  Max #  of tile  level_ picture size (CpbVclFactor or per AU of tiles columns idc MaxLumaPs CpbNalFactor (bits) MaxSlices- MaxTiles- MaxTile- Level value* (samples) Main tier High tier PerAu PerAu Cols 1.0 16 36 864 350 — 16 1 1 2.0 32 122 880 1 500 — 16 1 1 2.1 35 245 760 3 000 — 20 1 1 3.0 48 552 960 6 000 — 30 4 2 3.1 51 983 040 10 000 — 40 9 3 4.0 64 2 228 224 12 000 30 000 75 25 5 4.1 67 2 228 224 20 000 50 000 75 25 5 5.0 80 8 912 896 25 000 100 000 200 110 10 5.1 83 8 912 896 40 000 160 000 200 110 10 5.2 86 8 912 896 60 000 240 000 200 110 10 6.0 96 35 651 584 80 000 240 000 600 440 20 6.1 99 35 651 584 120 000 480 000 600 440 20 6.2 102 35 651 584 180 000 800 000 600 440 20 *For the level number in the form of major.minor, the value of general_level_idc for each of the above-listed levels is equal to major * 16 + minor * 3.

dpb_max_num_reorder_pics[i] specifies the maximum allowed number of pictures of the OLS that can precede any picture in the OLS in decoding order and follow that picture in output order when Htid is equal to i. The value of dpb_max_num_reorder_pics[i] shall be in the range of 0 to dpb_max_dec_pic_buffering_minusl [i], inclusive. When i is greater than 0, dpb_max_num_reorder_pics[i] shall be greater than or equal to dpb_max_num_reorder_pics[i−1]. When dpb_max_num_reorder_pics[i] is not present for i in the range of 0 to MaxSubLayersMinus1−1, inclusive, due to subLayerInfoFlag being equal to 0, it is inferred to be equal to dpb_max_num_reorder_pics[MaxSubLayersMinus1].

dpb_max_latency_increase_plus1[i] not equal to 0 is used to compute the value of MaxLatencyPictures[i], which specifies the maximum number of pictures in the OLS that can precede any picture in the OLS in output order and follow that picture in decoding order when Htid is equal to i.

When dpb_max_latency_increase_plus1 [i] is not equal to 0, the value of MaxLatencyPictures[i] is specified as follows:

MaxLatencyPictures[i]=dpb_max_num_reorder_pics[i]+dpb_max_latency_increase_plus1 [i]−1

When dpb_max_latency_increase_plus1 [i] is equal to 0, no corresponding limit is expressed.

The value of dpb_max_latency_increase_plus1 [i] shall be in the range of 0 to 2³²−2, inclusive. When dpb_max_latency_increase_plus1[i] is not present for i in the range of 0 to MaxSubLayersMinus1−1, inclusive, due to subLayerInfoFlag being equal to 0, it is inferred to be equal to dpb_max_latency_increase_plus1 [MaxSubLayersMinus1].

It should be noted that in JVET-S2001, the determination of MaxDpbSize is less than ideal as the value of maxDpbPicBuf is equal to 8 and the derivation of MaxDpbSize is based on previous standards where maxDpbPicBuf is equal to 6. Thus, the derivation of MaxDpbSize provided in JVET-S2001 is not consistent with maxDpbPicBuf being equal to 8. Further, it should be noted that for the case where the resulting value MaxDpbSize is 10, the comparison between PicSizeMaxlnSamplesY and MaxLumaPs as provided in JVET-S2001 unnecessarily excludes values of PicSizeMaxInSampleY.

FIG. 3 illustrates an example of a bitstream including multiple CVSs, where a CVS includes AUs, and AUs include picture units. The example illustrated in FIG. 3 corresponds to an example of encapsulating the slice NAL units illustrated in the example of FIG. 2 in a bitstream. In the example illustrated in FIG. 3 , the corresponding picture unit for Pic₃ includes the three VCL NAL coded slice NAL units, i.e., Slice® NAL unit, Slice₁ NAL unit, and Slice₂ NAL unit and two non-VCL NAL units, i.e., a PPS NAL Unit and a PH NAL unit. It should be noted that in FIG. 3 , HEADER is a NAL unit header (i.e., not to be confused with a slice header). Further, it should be noted that in FIG. 3 , other non-VCL NAL units, which are not illustrated may be included in the CVSs, e.g., SPS NAL units, VPS NAL units, SEI message NAL units, etc. Further, it should be noted that in other examples, a PPS NAL Unit used for decoding Pic₃ may be included elsewhere in the bitstream, e.g., in the picture unit corresponding to Pic₀ or may be provided by an external mechanism. As described in further detail below, in JVET-S2001, a PH syntax structure may be present in the slice header of a VCL NAL unit or in a PH NAL unit of the current PU.

It should be noted that generally, an Intra Random Access Point (IRAP) picture is a picture that does not refer to any pictures other than itself for prediction in its decoding process. In JVET-52001, an IRAP picture may be a clean random access (CRA) picture or an instantaneous decoder refresh (IDR) picture. In JVET-52001, the first picture in the bitstream in decoding order must be an IRAP or a gradual decoding refresh (GDR) picture. JVET-52001 describes the concept of a leading picture, which is a picture that precedes the associated IRAP picture in output order. JVET-52001 further describes the concept of a trailing picture which is a non-IRAP picture that follows the associated IRAP picture in output order. Trailing pictures associated with an IRAP picture also follow the IRAP picture in decoding order. For IDR pictures, there are no trailing pictures that require reference to a picture decoded prior to the IDR picture. JVET-S2001 provides where a CRA picture may have leading pictures that follow the CRA picture in decoding order and contain inter picture prediction references to pictures decoded prior to the CRA picture. Thus, when the CRA picture is used as a random access point these leading pictures may not be decodable and are identified as random access skipped leading (RASL) pictures. The other type of picture that can follow an IRAP picture in decoding order and precede it in output order is the random access decodable leading (RADL) picture, which cannot contain references to any pictures that precede the IRAP picture in decoding order.

FIG. 1 is a block diagram illustrating an example of a system that may be configured to code (i.e., encode and/or decode) video data according to one or more techniques of this disclosure. System 100 represents an example of a system that may encapsulate video data according to one or more techniques of this disclosure. As illustrated in FIG. 1 , system 100 includes source device 102, communications medium 110, and destination device 120. In the example illustrated in FIG. 1 , source device 102 may include any device configured to encode video data and transmit encoded video data to communications medium 110. Destination device 120 may include any device configured to receive encoded video data via communications medium 110 and to decode encoded video data. Source device 102 and/or destination device 120 may include computing devices equipped for wired and/or wireless communications and may include, for example, set top boxes, digital video recorders, televisions, desktop, laptop or tablet computers, gaming consoles, medical imagining devices, and mobile devices, including, for example, smartphones, cellular telephones, personal gaming devices.

Communications medium 110 may include any combination of wireless and wired communication media, and/or storage devices. Communications medium 110 may include coaxial cables, fiber optic cables, twisted pair cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other equipment that may be useful to facilitate communications between various devices and sites. Communications medium 110 may include one or more networks. For example, communications medium 110 may include a network configured to enable access to the World Wide Web, for example, the Internet. A network may operate according to a combination of one or more telecommunication protocols. Telecommunications protocols may include proprietary aspects and/or may include standardized telecommunication protocols. Examples of standardized telecommunications protocols include Digital Video Broadcasting (DVB) standards, Advanced Television Systems Committee (ATSC) standards, Integrated Services Digital Broadcasting (ISDB) standards, Data Over Cable Service Interface Specification (DOCSIS) standards, Global System Mobile Communications (GSM) standards, code division multiple access (CDMA) standards, 3rd Generation Partnership Project (3GPP) standards, European Telecommunications Standards Institute (ETSI) standards, Internet Protocol (IP) standards, Wireless Application Protocol (WAP) standards, and Institute of Electrical and Electronics Engineers (IEEE) standards.

Storage devices may include any type of device or storage medium capable of storing data. A storage medium may include a tangible or non-transitory computer-readable media. A computer readable medium may include optical discs, flash memory, magnetic memory, or any other suitable digital storage media. In some examples, a memory device or portions thereof may be described as non-volatile memory and in other examples portions of memory devices may be described as volatile memory. Examples of volatile memories may include random access memories (RAM), dynamic random access memories (DRAM), and static random access memories (SRAM). Examples of non-volatile memories may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. Storage device(s) may include memory cards (e.g., a Secure Digital (SD) memory card), internal/external hard disk drives, and/or internal/external solid state drives. Data may be stored on a storage device according to a defined file format.

FIG. 4 is a conceptual drawing illustrating an example of components that may be included in an implementation of system 100. In the example implementation illustrated in FIG. 4 , system 100 includes one or more computing devices 402A-402N, television service network 404, television service provider site 406, wide area network 408, local area network 410, and one or more content provider sites 412A-412N. The implementation illustrated in FIG. 4 represents an example of a system that may be configured to allow digital media content, such as, for example, a movie, a live sporting event, etc., and data and applications and media presentations associated therewith to be distributed to and accessed by a plurality of computing devices, such as computing devices 402A-402N. In the example illustrated in FIG. 4 , computing devices 402A-402N may include any device configured to receive data from one or more of television service network 404, wide area network 408, and/or local area network 410. For example, computing devices 402A-402N may be equipped for wired and/or wireless communications and may be configured to receive services through one or more data channels and may include televisions, including so-called smart televisions, set top boxes, and digital video recorders. Further, computing devices 402A-402N may include desktop, laptop, or tablet computers, gaming consoles, mobile devices, including, for example, “smart” phones, cellular telephones, and personal gaming devices.

Television service network 404 is an example of a network configured to enable digital media content, which may include television services, to be distributed. For example, television service network 404 may include public over-the-air television networks, public or subscription-based satellite television service provider networks, and public or subscription-based cable television provider networks and/or over the top or Internet service providers. It should be noted that although in some examples television service network 404 may primarily be used to enable television services to be provided, television service network 404 may also enable other types of data and services to be provided according to any combination of the telecommunication protocols described herein. Further, it should be noted that in some examples, television service network 404 may enable two-way communications between television service provider site 406 and one or more of computing devices 402A-402N. Television service network 404 may comprise any combination of wireless and/or wired communication media. Television service network 404 may include coaxial cables, fiber optic cables, twisted pair cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other equipment that may be useful to facilitate communications between various devices and sites. Television service network 404 may operate according to a combination of one or more telecommunication protocols. Telecommunications protocols may include proprietary aspects and/or may include standardized telecommunication protocols. Examples of standardized telecommunications protocols include DVB standards, ATSC standards, ISDB standards, DTMB standards, DMB standards, Data Over Cable Service Interface Specification (DOCSIS) standards, HbbTV standards, W3C standards, and UPnP standards.

Referring again to FIG. 4 , television service provider site 406 may be configured to distribute television service via television service network 404. For example, television service provider site 406 may include one or more broadcast stations, a cable television provider, or a satellite television provider, or an Internet-based television provider. For example, television service provider site 406 may be configured to receive a transmission including television programming through a satellite uplink/downlink. Further, as illustrated in FIG. 4 , television service provider site 406 may be in communication with wide area network 408 and may be configured to receive data from content provider sites 412A-412N. It should be noted that in some examples, television service provider site 406 may include a television studio and content may originate therefrom.

Wide area network 408 may include a packet based network and operate according to a combination of one or more telecommunication protocols. Telecommunications protocols may include proprietary aspects and/or may include standardized telecommunication protocols. Examples of standardized telecommunications protocols include Global System Mobile Communications (GSM) standards, code division multiple access (CDMA) standards, 3^(rd) Generation Partnership Project (3GPP) standards, European Telecommunications Standards Institute (ETSI) standards, European standards (EN), IP standards, Wireless Application Protocol (WAP) standards, and Institute of Electrical and Electronics Engineers (IEEE) standards, such as, for example, one or more of the IEEE 802 standards (e.g., Wi-Fi). Wide area network 408 may comprise any combination of wireless and/or wired communication media. Wide area network 408 may include coaxial cables, fiber optic cables, twisted pair cables, Ethernet cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other equipment that may be useful to facilitate communications between various devices and sites. In one example, wide area network 408 may include the Internet. Local area network 410 may include a packet based network and operate according to a combination of one or more telecommunication protocols. Local area network 410 may be distinguished from wide area network 408 based on levels of access and/or physical infrastructure. For example, local area network 410 may include a secure home network.

Referring again to FIG. 4 , content provider sites 412A-412N represent examples of sites that may provide multimedia content to television service provider site 406 and/or computing devices 402A-402N. For example, a content provider site may include a studio having one or more studio content servers configured to provide multimedia files and/or streams to television service provider site 406. In one example, content provider sites 412A-412N may be configured to provide multimedia content using the IP suite. For example, a content provider site may be configured to provide multimedia content to a receiver device according to Real Time Streaming Protocol (RTSP), HTTP, or the like. Further, content provider sites 412A-412N may be configured to provide data, including hypertext based content, and the like, to one or more of receiver devices computing devices 402A-402N and/or television service provider site 406 through wide area network 408. Content provider sites 412A-412N may include one or more web servers. Data provided by data provider site 412A-412N may be defined according to data formats.

Referring again to FIG. 1 , source device 102 includes video source 104, video encoder 106, data encapsulator 107, and interface 108. Video source 104 may include any device configured to capture and/or store video data. For example, video source 104 may include a video camera and a storage device operably coupled thereto. Video encoder 106 may include any device configured to receive video data and generate a compliant bitstream representing the video data. A compliant bitstream may refer to a bitstream that a video decoder can receive and reproduce video data therefrom. Aspects of a compliant bitstream may be defined according to a video coding standard. When generating a compliant bitstream video encoder 106 may compress video data. Compression may be lossy (discernible or indiscernible to a viewer) or lossless. FIG. 5 is a block diagram illustrating an example of video encoder 500 that may implement the techniques for encoding video data described herein. It should be noted that although example video encoder 500 is illustrated as having distinct functional blocks, such an illustration is for descriptive purposes and does not limit video encoder 500 and/or sub-components thereof to a particular hardware or software architecture. Functions of video encoder 500 may be realized using any combination of hardware, firmware, and/or software implementations.

Video encoder 500 may perform intra prediction coding and inter prediction coding of picture areas, and, as such, may be referred to as a hybrid video encoder. In the example illustrated in FIG. 5 , video encoder 500 receives source video blocks. In some examples, source video blocks may include areas of picture that has been divided according to a coding structure. For example, source video data may include macroblocks, CTUs, CBs, sub-divisions thereof, and/or another equivalent coding unit. In some examples, video encoder 500 may be configured to perform additional sub-divisions of source video blocks. It should be noted that the techniques described herein are generally applicable to video coding, regardless of how source video data is partitioned prior to and/or during encoding. In the example illustrated in FIG. 5 , video encoder 500 includes summer 502, transform coefficient generator 504, coefficient quantization unit 506, inverse quantization and transform coefficient processing unit 508, summer 510, intra prediction processing unit 512, inter prediction processing unit 514, filter unit 516, and entropy encoding unit 518. As illustrated in FIG. 5 , video encoder 500 receives source video blocks and outputs a bitstream.

In the example illustrated in FIG. 5 , video encoder 500 may generate residual data by subtracting a predictive video block from a source video block. The selection of a predictive video block is described in detail below. Summer 502 represents a component configured to perform this subtraction operation. In one example, the subtraction of video blocks occurs in the pixel domain. Transform coefficient generator 504 applies a transform, such as a discrete cosine transform (DCT), a discrete sine transform (DST), or a conceptually similar transform, to the residual block or sub-divisions thereof (e.g., four 8×8 transforms may be applied to a 16×16 array of residual values) to produce a set of residual transform coefficients. Transform coefficient generator 504 may be configured to perform any and all combinations of the transforms included in the family of discrete trigonometric transforms, including approximations thereof. Transform coefficient generator 504 may output transform coefficients to coefficient quantization unit 506. Coefficient quantization unit 506 may be configured to perform quantization of the transform coefficients. The quantization process may reduce the bit depth associated with some or all of the coefficients. The degree of quantization may alter the rate-distortion (i.e., bit-rate vs. quality of video) of encoded video data. The degree of quantization may be modified by adjusting a quantization parameter (QP). A quantization parameter may be determined based on slice level values and/or CU level values (e.g., CU delta QP values). QP data may include any data used to determine a QP for quantizing a particular set of transform coefficients. As illustrated in FIG. 5 , quantized transform coefficients (which may be referred to as level values) are output to inverse quantization and transform coefficient processing unit 508. Inverse quantization and transform coefficient processing unit 508 may be configured to apply an inverse quantization and an inverse transformation to generate reconstructed residual data. As illustrated in FIG. 5 , at summer 510, reconstructed residual data may be added to a predictive video block. In this manner, an encoded video block may be reconstructed and the resulting reconstructed video block may be used to evaluate the encoding quality for a given prediction, transformation, and/or quantization. Video encoder 500 may be configured to perform multiple coding passes (e.g., perform encoding while varying one or more of a prediction, transformation parameters, and quantization parameters). The rate-distortion of a bitstream or other system parameters may be optimized based on evaluation of reconstructed video blocks. Further, reconstructed video blocks may be stored and used as reference for predicting subsequent blocks.

Referring again to FIG. 5 , intra prediction processing unit 512 may be configured to select an intra prediction mode for a video block to be coded. Intra prediction processing unit 512 may be configured to evaluate a frame and determine an intra prediction mode to use to encode a current block. As described above, possible intra prediction modes may include planar prediction modes, DC prediction modes, and angular prediction modes. Further, it should be noted that in some examples, a prediction mode for a chroma component may be inferred from a prediction mode for a luma prediction mode. Intra prediction processing unit 512 may select an intra prediction mode after performing one or more coding passes. Further, in one example, intra prediction processing unit 512 may select a prediction mode based on a rate-distortion analysis. As illustrated in FIG. 5 , intra prediction processing unit 512 outputs intra prediction data (e.g., syntax elements) to entropy encoding unit 518 and transform coefficient generator 504. As described above, a transform performed on residual data may be mode dependent (e.g., a secondary transform matrix may be determined based on a prediction mode).

Referring again to FIG. 5 , inter prediction processing unit 514 may be configured to perform inter prediction coding for a current video block. Inter prediction processing unit 514 may be configured to receive source video blocks and calculate a motion vector for PUs of a video block. A motion vector may indicate the displacement of a prediction unit of a video block within a current video frame relative to a predictive block within a reference frame. Inter prediction coding may use one or more reference pictures. Further, motion prediction may be uni-predictive (use one motion vector) or bi-predictive (use two motion vectors). Inter prediction processing unit 514 may be configured to select a predictive block by calculating a pixel difference determined by, for example, sum of absolute difference (SAD), sum of square difference (SSD), or other difference metrics. As described above, a motion vector may be determined and specified according to motion vector prediction. Inter prediction processing unit 514 may be configured to perform motion vector prediction, as described above. Inter prediction processing unit 514 may be configured to generate a predictive block using the motion prediction data. For example, inter prediction processing unit 514 may locate a predictive video block within a frame buffer (not shown in FIG. 5 ). It should be noted that inter prediction processing unit 514 may further be configured to apply one or more interpolation filters to a reconstructed residual block to calculate sub-integer pixel values for use in motion estimation. Inter prediction processing unit 514 may output motion prediction data for a calculated motion vector to entropy encoding unit 518.

As described above, the scaling function for MMVD scaling provided in JVET-52001 is less than ideal. In one example, according to the techniques herein, the scale factor may be set to 1 in the case where inter-layer prediction is utilized for one of two predictions. A scale factor being set to 1 is equivalent to not applying scaling. That is, according to the techniques herein, in one example, a process for deriving motion vector differences may be based on the following:

Inputs to this process are:

-   -   a luma location (xCb, yCb) of the top-left sample of the current         luma coding block relative to the top-left luma sample of the         current picture,     -   reference indices refldxL0 and refldxL1,     -   prediction list utilization flags predFlagL0 and predFlagL1.         Outputs of this process are the luma merge motion vector         differences in 1/16 fractional-sample accuracy mMvdL0 and         mMvdL1.         The variable currPic specifies the current picture.         The luma merge motion vector differences mMvdL0 and mMvdL1 are         derived as follows:     -   If both predFlagL0 and predFlagL1 are equal to 1, the following         applies:         -   currPocDiffL0=DiffPicOrderCnt(currPic,             RefPicList[0][refldxL0])         -   currPocDiffL1=DiffPicOrderCnt(currPic,             RefPicList[1][refldxL1])     -   If currPocDiffL0 is equal to currPocDiffL1 or currPocDiffL0 is         equal to 0 or currPocDiffL1 is equal to 0, the following         applies:         -   mMvdL0[0]=MmvdOffset[xCb][yCb][0]             -   mMvdL0[1]=MmvdOffset[xCb][yCb][1]             -   mMvdL1[0]=MmvdOffset[xCb][yCb][0]             -   mMvdL1[1]=MmvdOffset[xCb][yCb][1]         -   Otherwise, if Abs(currPocDiffL0) is greater than or equal to             Abs(currPocDiffL1), the following applies:             -   mMvdL0[0]=MmvdOffset[xCb][yCb][0]             -   mMvdL0[1]=MmvdOffset[xCb][yCb][1]         -   If RefPicList[0][refldxL0] is not an LTRP and             RefPicList[1][refldxL1] is not an LTRP, the following             applies:             -   td=Clip3(−128, 127, currPocDiffL0)             -   tb=Clip3(−128, 127, currPocDiffL1)             -   tx=(16384+(Abs(td)»1))/td             -   distScaleFactor=Clip3(−4096, 4095, (tb*tx+32)»6)             -   mMvdL1[0]=Clip3(−2¹⁷, 2¹⁷−1,                 (distScaleFactor*mMvdL0[0]+128−(distScaleFactor*mMvdL0[0]>=0))»8)             -   mMvdL1[1]=Clip3(−2¹⁷, 2¹⁷−1,                 (distScaleFactor*mMvdL0[1]+128−(distScaleFactor*mMvdL0[1]>=0))»8)         -   Otherwise, the following applies:             -   mMvdL1[0]=Sign(currPocDiffL0)==Sign(currPocDiffL1)?                 -   mMvdL0[0]:−mMvdL0[0]             -   mMvdL1[1]=Sign(currPocDiffL0)==Sign(currPocDiffL1)?                 -   mMvdL0[1]:−mMvdL0[1]         -   Otherwise (Abs(currPocDiffL0) is less than             Abs(currPocDiffL1)), the following applies:             -   mMvdL1[0]=MmvdOffset[xCb][yCb][0]             -   mMvdL1[1]=MmvdOffset[xCb][yCb][1]         -   If RefPicList[0][refldxL0] is not an LTRP and             RefPicList[1][refldxL1] is not an LTRP, the following             applies:             -   td=Clip3(−128, 127, currPocDiffL1)             -   tb=Clip3(−128, 127, currPocDiffL0)             -   tx=(16384+(Abs(td)»1))/td             -   distScaleFactor=Clip3(−4096, 4095, (tb*tx+32)»6)             -   mMvdL0[0]=Clip3(−2¹⁷, 2¹⁷−1, (distScaleFactor*mMvdL1                 [0]+128−(distScaleFactor*mMvdL1 [0]>=0))»8)             -   mMvdL0[1]=Clip3(−2¹⁷, 2¹⁷−1,                 (distScaleFactor*mMvdL1[1]+128−(distScaleFactor*mMvdL1[1]>=0))»8))         -   Otherwise, the following applies:             -   mMvdL0[0]=Sign(currPocDiffL0)==Sign(currPocDiffL1)?                 -   mMvdL1[0]:−mMvdL1[0]             -   mMvdL0[1]=Sign(currPocDiffL0)==Sign(currPocDiffL1)?                 -   mMvdL1[ 1]:−mMvdL1[ 1]     -   Otherwise (predFlagL0 or predFlagL1 are equal to 1), the         following applies for X being 0 and 1:         -   mMvdLX[0]=(predFlagLX==1)? MmvdOffset[xCb][yCb][0]:0         -   mMvdLX[1]=(predFlagLX==1)? MmvdOffset[xCb][yCb][1]:0

In one example, according to the techniques herein, a process for deriving motion vector differences may be based on the following:

Inputs to this process are:

-   -   a luma location (xCb, yCb) of the top-left sample of the current         luma coding block relative to the top-left luma sample of the         current picture,     -   reference indices refldxL0 and refldxL1,     -   prediction list utilization flags predFlagL0 and predFlagL1.         Outputs of this process are the luma merge motion vector         differences in 1/16 fractional-sample accuracy mMvdL0 and         mMvdL1.         The variable currPic specifies the current picture.         The luma merge motion vector differences mMvdL0 and mMvdL1 are         derived as follows:     -   If both predFlagL0 and predFlagL1 are equal to 1, the following         applies:         -   currPocDiffL0=DiffPicOrderCnt(currPic,             RefPicList[0][refldxL0])         -   currPocDiffL1=DiffPicOrderCnt(currPic,             RefPicList[1][refldxL1])     -   If currPocDiffL0 is equal to currPocDiffL1, the following         applies:         -   mMvdL0[0]=MmvdOffset[xCb][yCb][0]         -   mMvdL0[1]=MmvdOffset[xCb][yCb][1]         -   mMvdL1[0]=MmvdOffset[xCb][yCb][0]         -   mMvdL1[1]=MmvdOffset[xCb][yCb][1]     -   Otherwise, if Abs(currPocDiffL0) is greater than or equal to         Abs(currPocDiffL1), the following applies:         -   mMvdL0[0]=MmvdOffset[xCb][yCb][0]         -   mMvdL0[1]=MmvdOffset[xCb][yCb][1]     -   If RefPicList[0][refldxL0] is not marked as “used for long-term         reference” and RefPicList[1][refldxL1] is not marked as “used         for long-term reference”, the following applies:         -   td=Clip3(−128, 127, currPocDiffL0)         -   tb=Clip3(−128, 127, currPocDiffL1)         -   tx=(16384+(Abs(td)»1))/td         -   distScaleFactor=Clip3(−4096, 4095, (tb*tx+32)»6)         -   mMvdL1[0]=Clip3(−2′⁷, 2′−1,             (distScaleFactor*mMvdL0[0]+128−(distScaleFactor*mMvdL0[0]>=0))»8)         -   mMvdL1[1]=Clip3(−2′⁷, 2¹⁷−1,             (distScaleFactor*mMvdL0[1]+128−(distScaleFactor*mMvdL0[1]>=0))»8)     -   Otherwise, the following applies:         -   mMvdL1[0]=Sign(currPocDiffL0)==−Sign(currPocDiffL1)?             -   −mMvdL0[0]:mMvdL0[0]         -   mMvdL1[1]=Sign(currPocDiffL0)==−Sign(currPocDiffL1)?             -   −mMvdL0[1]:mMvdL0[1]     -   Otherwise (Abs(currPocDiffL0) is less than Abs(currPocDiffL1)),         the following applies:         -   mMvdL1[0]=MmvdOffset[xCb][yCb][0]         -   mMvdL1[1]=MmvdOffset[xCb][yCb][1]     -   If RefPicList[0][refldxL0] is not marked as “used for long-term         reference” and         -   RefPicList[1][refldxL1] is not marked as “used for long-term             reference”, the following applies:         -   td=Clip3(−128, 127, currPocDiffL1)         -   tb=Clip3(−128, 127, currPocDiffL0)         -   tx=(16384+(Abs(td)»1))/td         -   distScaleFactor=Clip3(−4096, 4095, (tb*tx+32)»6)         -   mMvdL0[0]=Clip3(−2¹⁷, 2¹⁷−1,             (distScaleFactor*mMvdL1[0]+128−(distScaleFactor*mMvdL1[0]>=0))»8)         -   mMvdL0[1]=Clip3(−2¹⁷, 2¹⁷−1,             (distScaleFactor*mMvdL1[1]+128−(distScaleFactor*mMvdL1[1]>=0))»8))     -   Otherwise, the following applies:         -   mMvdL0[0]=Sign(currPocDiffL0)==−Sign(currPocDiffL1)?             -   −mMvdL1[0]:mMvdL1[0]         -   mMvdL0[1]=Sign(currPocDiffL0)==−Sign(currPocDiffL1)?             -   −mMvdL1[ 1]:mMvdL1[ 1]     -   Otherwise (predFlagL0 or predFlagL1 are equal to 1), the         following applies for X being 0 and 1:         -   mMvdLX[0]=(predFlagLX==1)? MmvdOffset[xCb][yCb][0]:0         -   mMvdLX[1]=(predFlagLX==1)? MmvdOffset[xCb][yCb][1]:0

It should be noted that both of the example processes for deriving motion vector differences provided above effectively set the scale factor to 1 in the case where inter-layer prediction is signaled.

As described above, in JVET-S2001, the determination of MaxDpbSize is less than ideal. In one example, according to the techniques herein, the determination of MaxDpbSize may be based on the following, which results in values of MaxDpbSize of either 8, 10, 12 or 16:

  if( 2 * PicSizeMaxInSamplesY <= MaxLumaPs )  MaxDpbSize = 2 * maxDpbPicBuf else if( 3 * PicSizeMaxInSamplesY <= 2 * MaxLumaPs )  MaxDpbSize = 3 * maxDpbPicBuf / 2 else if( 5 * PicSizeMaxInSamplesY <= 4 * MaxLumaPs )  MaxDpbSize = 5 * maxDpbPicBuf / 4 else  MaxDpbSize = maxDpbPicBuf

In one example, according to the techniques herein, the determination of MaxDpbSize may be based on the following, which results in values of MaxDpbSize of either 8, 10 or 16:

  if( 2 * PicSizeMaxInSamplesY <= MaxLumaPs )  MaxDpbSize = 2 * maxDpbPicBuf else if( 5 * PicSizeMaxInSamplesY <= 4 * MaxLumaPs )  MaxDpbSize = 5 * maxDpbPicBuf / 4 else  MaxDpbSize = maxDpbPicBuf

In one example, according to the techniques herein, the determination of MaxDpbSize may be based on the following, which results in values of MaxDpbSize of either 8, 12 or 16:

  if( 2 * PicSizeMaxInSamplesY <= MaxLumaPs )  MaxDpbSize = 2 * maxDpbPicBuf else if( 3 * PicSizeMaxInSamplesY <= 2 * MaxLumaPs )  MaxDpbSize = 3 * maxDpbPicBuf / 2 else  MaxDpbSize = maxDpbPicBuf

In one example, according to the techniques herein, the determination of MaxDpbSize may be based on the following, which results in values of MaxDpbSize of either 8, 10 or 16:

  if( 2 * PicSizeMaxInSamplesY <= MaxLumaPs )  MaxDpbSize = 2 * maxDpbPicBuf else if( 4 * PicSizeMaxInSamplesY <= 3 * MaxLumaPs )  MaxDpbSize = 4 * maxDpbPicBuf / 3 else  MaxDpbSize = maxDpbPicBuf

Referring again to FIG. 5 , filter unit 516 receives reconstructed video blocks and coding parameters and outputs modified reconstructed video data. Filter unit 516 may be configured to perform deblocking and/or Sample Adaptive Offset (SAO) filtering. SAO filtering is a non-linear amplitude mapping that may be used to improve reconstruction by adding an offset to reconstructed video data. It should be noted that as illustrated in FIG. 5 , intra prediction processing unit 512 and inter prediction processing unit 514 may receive modified reconstructed video block via filter unit 216. Entropy encoding unit 518 receives quantized transform coefficients and predictive syntax data (i.e., intra prediction data and motion prediction data). It should be noted that in some examples, coefficient quantization unit 506 may perform a scan of a matrix including quantized transform coefficients before the coefficients are output to entropy encoding unit 518. In other examples, entropy encoding unit 518 may perform a scan. Entropy encoding unit 518 may be configured to perform entropy encoding according to one or more of the techniques described herein. In this manner, video encoder 500 represents an example of a device configured to determine whether a reference picture associated with a motion vector prediction candidate is an inter-layer reference picture and set a scaling factor to one in the case where the a reference picture is an inter-layer reference picture.

Referring again to FIG. 1 , data encapsulator 107 may receive encoded video data and generate a compliant bitstream, e.g., a sequence of NAL units according to a defined data structure. A device receiving a compliant bitstream can reproduce video data therefrom. Further, as described above, sub-bitstream extraction may refer to a process where a device receiving a compliant bitstream forms a new compliant bitstream by discarding and/or modifying data in the received bitstream. It should be noted that the term conforming bitstream may be used in place of the term compliant bitstream. In one example, data encapsulator 107 may be configured to generate syntax according to one or more techniques described herein. It should be noted that data encapsulator 107 need not necessary be located in the same physical device as video encoder 106. For example, functions described as being performed by video encoder 106 and data encapsulator 107 may be distributed among devices illustrated in FIG. 4 .

Referring again to FIG. 1 , interface 108 may include any device configured to receive data generated by data encapsulator 107 and transmit and/or store the data to a communications medium. Interface 108 may include a network interface card, such as an Ethernet card, and may include an optical transceiver, a radio frequency transceiver, or any other type of device that can send and/or receive information. Further, interface 108 may include a computer system interface that may enable a file to be stored on a storage device. For example, interface 108 may include a chipset supporting Peripheral Component Interconnect (PCI) and Peripheral Component Interconnect Express (PCIe) bus protocols, proprietary bus protocols, Universal Serial Bus (USB) protocols, I²C, or any other logical and physical structure that may be used to interconnect peer devices.

Referring again to FIG. 1 , destination device 120 includes interface 122, data decapsulator 123, video decoder 124, and display 126. Interface 122 may include any device configured to receive data from a communications medium. Interface 122 may include a network interface card, such as an Ethernet card, and may include an optical transceiver, a radio frequency transceiver, or any other type of device that can receive and/or send information. Further, interface 122 may include a computer system interface enabling a compliant video bitstream to be retrieved from a storage device. For example, interface 122 may include a chipset supporting PCI and PCIe bus protocols, proprietary bus protocols, USB protocols, I²C, or any other logical and physical structure that may be used to interconnect peer devices. Data decapsulator 123 may be configured to receive and parse any of the example syntax structures described herein.

Video decoder 124 may include any device configured to receive a bitstream (e.g., a sub-bitstream extraction) and/or acceptable variations thereof and reproduce video data therefrom. Display 126 may include any device configured to display video data. Display 126 may comprise one of a variety of display devices such as a liquid crystal display (LCD), a plasma display, an organic light emitting diode (OLED) display, or another type of display. Display 126 may include a High Definition display or an Ultra High Definition display. It should be noted that although in the example illustrated in FIG. 1 , video decoder 124 is described as outputting data to display 126, video decoder 124 may be configured to output video data to various types of devices and/or sub-components thereof. For example, video decoder 124 may be configured to output video data to any communication medium, as described herein.

FIG. 6 is a block diagram illustrating an example of a video decoder that may be configured to decode video data according to one or more techniques of this disclosure (e.g., the decoding process for reference-picture list construction described above). In one example, video decoder 600 may be configured to decode transform data and reconstruct residual data from transform coefficients based on decoded transform data. Video decoder 600 may be configured to perform intra prediction decoding and inter prediction decoding and, as such, may be referred to as a hybrid decoder. Video decoder 600 may be configured to parse any combination of the syntax elements described above in Tables 1-5. Video decoder 600 may decode a picture based on or according to the processes described above, and further based on parsed values in Tables 1-5.

In the example illustrated in FIG. 6 , video decoder 600 includes an entropy decoding unit 602, inverse quantization unit 604, inverse transform coefficient processing unit 606, intra prediction processing unit 608, inter prediction processing unit 610, summer 612, post filter unit 614, and reference buffer 616. Video decoder 600 may be configured to decode video data in a manner consistent with a video coding system. It should be noted that although example video decoder 600 is illustrated as having distinct functional blocks, such an illustration is for descriptive purposes and does not limit video decoder 600 and/or sub-components thereof to a particular hardware or software architecture. Functions of video decoder 600 may be realized using any combination of hardware, firmware, and/or software implementations.

As illustrated in FIG. 6 , entropy decoding unit 602 receives an entropy encoded bitstream. Entropy decoding unit 602 may be configured to decode syntax elements and quantized coefficients from the bitstream according to a process reciprocal to an entropy encoding process. Entropy decoding unit 602 may be configured to perform entropy decoding according any of the entropy coding techniques described above. Entropy decoding unit 602 may determine values for syntax elements in an encoded bitstream in a manner consistent with a video coding standard. As illustrated in FIG. 6 , entropy decoding unit 602 may determine a quantization parameter, quantized coefficient values, transform data, and prediction data from a bitstream. In the example, illustrated in FIG. 6 , inverse quantization unit 604 and inverse transform coefficient processing unit 606 receives a quantization parameter, quantized coefficient values, transform data, and prediction data from entropy decoding unit 602 and outputs reconstructed residual data.

Referring again to FIG. 6 , reconstructed residual data may be provided to summer 612. Summer 612 may add reconstructed residual data to a predictive video block and generate reconstructed video data. A predictive video block may be determined according to a predictive video technique (i.e., intra prediction and inter frame prediction). Intra prediction processing unit 608 may be configured to receive intra prediction syntax elements and retrieve a predictive video block from reference buffer 616. Reference buffer 616 may include a memory device configured to store one or more frames of video data. Intra prediction syntax elements may identify an intra prediction mode, such as the intra prediction modes described above. Inter prediction processing unit 610 may receive inter prediction syntax elements and generate motion vectors to identify a prediction block in one or more reference frames stored in reference buffer 616. Inter prediction processing unit 610 may produce motion compensated blocks, possibly performing interpolation based on interpolation filters. Identifiers for interpolation filters to be used for motion estimation with sub-pixel precision may be included in the syntax elements. Inter prediction processing unit 610 may use interpolation filters to calculate interpolated values for sub-integer pixels of a reference block. Post filter unit 614 may be configured to perform filtering on reconstructed video data. For example, post filter unit 614 may be configured to perform deblocking and/or Sample Adaptive Offset (SAO) filtering, e.g., based on parameters specified in a bitstream. Further, it should be noted that in some examples, post filter unit 614 may be configured to perform proprietary discretionary filtering (e.g., visual enhancements, such as, mosquito noise reduction). As illustrated in FIG. 6 , a reconstructed video block may be output by video decoder 600. In this manner, video decoder 600 represents an example of a device configured to determine whether a reference picture associated with a motion vector prediction candidate is an inter-layer reference picture and set a scaling factor to one in the case where the reference picture is an inter-layer reference picture.

In one or more examples, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which corresponds to a tangible medium such as data storage media, or communication media including any medium that facilitates transfer of a computer program from one place to another, e.g., according to a communication protocol. In this manner, computer-readable media generally may correspond to (1) tangible computer-readable storage media which is non-transitory or (2) a communication medium such as a signal or carrier wave. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, code and/or data structures for implementation of the techniques described in this disclosure. A computer program product may include a computer-readable medium.

By way of example, and not limitation, such computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. It should be understood, however, that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transitory media, but are instead directed to non-transitory, tangible storage media. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Accordingly, the term “processor,” as used herein may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein. In addition, in some aspects, the functionality described herein may be provided within dedicated hardware and/or software modules configured for encoding and decoding, or incorporated in a combined codec. Also, the techniques could be fully implemented in one or more circuits or logic elements.

The techniques of this disclosure may be implemented in a wide variety of devices or apparatuses, including a wireless handset, an integrated circuit (IC) or a set of ICs (e.g., a chip set). Various components, modules, or units are described in this disclosure to emphasize functional aspects of devices configured to perform the disclosed techniques, but do not necessarily require realization by different hardware units. Rather, as described above, various units may be combined in a codec hardware unit or provided by a collection of interoperative hardware units, including one or more processors as described above, in conjunction with suitable software and/or firmware.

Moreover, each functional block or various features of the base station device and the terminal device used in each of the aforementioned embodiments may be implemented or executed by a circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or each circuit described above may be configured by a digital circuit or may be configured by an analogue circuit. Further, when a technology of making into an integrated circuit superseding integrated circuits at the present time appears due to advancement of a semiconductor technology, the integrated circuit by this technology is also able to be used.

Various examples have been described. These and other examples are within the scope of the following claims. 

What is claimed is:
 1. A method of encoding video data, the method comprising encoding a syntax element, wherein the syntax element plus 1 specifying a maximum required size of a decoded picture buffer in units of picture storage buffers, wherein parsing the syntax element includes deriving a range of values for the syntax element, wherein an upper range value of the syntax element is set to one of: 15, 11, or 7 according to the following: if a product of 2 times PicSizeMaxlnSamplesY is less than or equal to a maximum luma picture size of a specified level of video, the upper range value is set to 15, otherwise, if a product of 3 times PicSizeMaxlnSamplesY is less than or equal to a product of 2 times the maximum luma picture size of the specified level of video, the upper range value is set to 11, otherwise, the upper range value is set to
 7. 2. A device of encoding video data comprising one or more processors configured to encode a syntax element, wherein the syntax element plus 1 specifying a maximum required size of a decoded picture buffer in units of picture storage buffers, wherein parsing the syntax element includes deriving a range of values for the syntax element, wherein an upper range value of the syntax element is set to one of: 15, 11, or 7 according to the following: if a product of 2 times PicSizeMaxlnSamplesY is less than or equal to a maximum luma picture size of a specified level of video, the upper range value is set to 15, otherwise, if a product of 3 times PicSizeMaxlnSamplesY is less than or equal to a product of 2 times the maximum luma picture size of the specified level of video, the upper range value is set to 11, otherwise, the upper range value is set to
 7. 3. A method of determining a maximum required size of a decoded picture buffer for coding video data, the method comprising: parsing a syntax element, wherein the syntax element plus 1 specifying the maximum required size of the decoded picture buffer in units of picture storage buffers, wherein parsing the syntax element includes deriving a range of values for the syntax element, wherein an upper range value of the syntax element is set to one of: 15, 11, or 7 according to the following: if a product of 2 times PicSizeMaxlnSamplesY is less than or equal to a maximum luma picture size of a specified level of video, the upper range value is set to 15, otherwise, if a product of 3 times PicSizeMaxlnSamplesY is less than or equal to a product of 2 times the maximum luma picture size of the specified level of video, the upper range value is set to 11, otherwise, the upper range value is set to
 7. 